can xfs_repair guarantee a complete clean filesystem?

[Eric Sandeen]

hank peng wrote:

> Today, I encountered a problem:
> I use "xfs_repair -L “ on a damaged filesystem and a lot of messages

why did you use -L, did it fail to mount & replay the log properly?

> output which include "moving disconnected inodes to lost+found ...".
> Then I can remount the filesystem successfully and decided to remove
> those files in lost+found directory, but it printed the following
> message:
> root at 1234dahua:/mnt/Pool_md1/ss1/lost+found# rm -rf *
> rm: cannot stat '710': Structure needs cleaning
> rm: cannot stat '728': Structure needs cleaning
> rm: cannot stat '729': Structure needs cleaning
> rm: cannot stat '730': Structure needs cleaning
> rm: cannot stat '731': Structure needs cleaning
> rm: cannot stat '732': Structure needs cleaning
> rm: cannot stat '733': Structure needs cleaning
> rm: cannot stat '734': Structure needs cleaning
> rm: cannot stat '735': Structure needs cleaning

Look at dmesg to see what's gone wrong....

> Other directories and files seems normal to access, is it not allowed
> to delete files in lost+found directory after repair, then what should
> I do?

This is indicative of a bug or IO error that caused xfs to shut down.

You haven't mentioned which kernel version, architecture, or
version of xfsprogs you're using yet ... that may offer some clues.

I'm guessing an older kernel and userspace on arm? :)

-Eric