Re: xfs_scrub: inode record: Attempting optimization

["Darrick J. Wong" <djwong@kernel.org>]

On Wed, Oct 26, 2022 at 09:53:30AM +0200, Matthias Bodenbinder wrote:
> Hello,
> 
> I am not sure if this is the right place to ask my question. If not
> please forgive me and point me to the correct place.
> 
> I have a question about xfs_scrub. When I run this on my root directory
> I get plenty of info messages like:
> 
> ####
> # xfs_scrub -v / 
> EXPERIMENTAL xfs_scrub program in use! Use at your own risk!
> Phase 1: Find filesystem geometry.
> /: using 24 threads to scrub.
> Phase 2: Check internal metadata.
> Phase 3: Scan all inodes.
> Phase 4: Repair filesystem.
> Info: inode 100663763 (3/467) inode record: Attempting optimization.
> Info: inode 67169419 (2/60555) inode record: Attempting optimization.
> Info: inode 33566167 (1/11735) inode record: Attempting optimization.
> ...
> 
> Phase 5: Check directory tree.
> Phase 7: Check summary counters.
> 44,0GiB data used;  1,2M inodes used.
> 43,6GiB data found; 1,2M inodes found.
> 1,2M inodes counted; 1,2M inodes checked.
> ####
> 
> 
> I see more than 3200 Info lines like this. And they occur also with any
> subsequent scrub. They are not going away.
> 
> Can I fix this somehow or shall I just ignore it?

Unfortunately, the *repair* part of online fsck isn't upstream yet, so
the kernel doesn't actually know how to fix or optimize anything.

For now, you might as well run scrub in dry-run mode (-n) which should
cut down on the warnings.

(Though TBH there's not really much point in running xfs_scrub until I
can get all ~480 patches through the review process -- there are 100
pending fixes and strengthening patches for the checking part alone.)

That said -- thanks for trying it out! :)

--D

> Kind Regards
> Matthias
> 
> PS
> This is on EndeavourOS with kernel 5.15.74-lts
>