On Thu, Dec 24, 2020 at 11:05 PM Felix Miata <mrmazda(a)earthlink.net> wrote:
Since I've been seeing it on other installations, I timed this one:
real 7m31s
user 7m8.9s
sys 0m30.2s
I started seeing it with the early 5.9-rc's. But haven't seen it since
release versions. In my case top shows depmod and weak-modules; and
many small files being created and destroyed in a loop. [1] But
haven't seen it in a while or with any of the 5.10 or 5.11 kernels.
If you aren't seeing those indications: Do you have any 3rd party
modules that depend on dkms? Are you running a 5.10 series kernel at
the time, and is sysroot btrfs? [2]
[1]
Install fatrace and run it with sudo. It works on any file system but
it doesn't show file sizes, just path to file.
A btrfs specific way of find this info, with inode, size, and path:
First get the current generation value for the subvolume you want to
find recent files.
# btrfs sub list -t /
ID gen top level path
-- --- --------- ----
258 1574871 5 home
339 1568566 5 boot
429 1574871 5 root
It's 1574871. This increments with each transaction, and a transaction
is 30 seconds unless some process does fsync (which I don't think the
kernel install uses until the very end). Next...
# btrfs sub find / 1574870
Note it's one value less, as an example. And you'll get a bunch of
lines representing files that have been created or modified since the
specified generation value. The current generation is incrementing as
time goes on so you can bump up the value of the generation you
specify to keep the output short, and thus recent.
--
Chris Murphy