[Pvfs2-users] pvfs2-fsck no-fix run shows possible trouble

[Bill Wichser]

In attempting to correct our client nodes' problem of kernel crashes 
from a previous thread, we had succesfully run the pvfs2-fsck command on 
the filesystem, finding on the order of double digit terabytes of files 
placed into the lost+found directory.

Shortly after returning this filesystem to service, we ran another 
pvfs2-fsck check, this time in "no-fix" mode and found a number of 
possible problems still remaining.

260 lines in pass 2 stating something like:

* not removing None 129782812.
* not removing None 130114701.
* not removing None 129782831.

Plus 124 lines in pass 4 with something like:

* not removing Datafile 259929009.
* not removing Datafile 259929004.
* not removing Datafile 260301031.

All these lines have an asterisk prefix, which I understood meant a
problem, and had this been a "fix" run, all these "None" and "Datafile"
entries would have been removed.


Now a week later when we run the pvfs2-fsck again in "no-fix" mode, we 
are still seeing these messages, which means that nothing more bad is 
apparently happening but that there still appears to be corruption.

Am I interpreting things correctly?  Or are these errors still possible 
remnants of all the files still sitting in the lost+found directory 
which await removal?

Thanks,
Bill