Eric Sandeen wrote:
> These are all good questions ;) TBH I'm kind of digging through repair
> in earnest for the first time. I'm not certain why it got into this
> state, whether there is some underlying bug, perhaps leaving things
> wrongly referenced, or just a plain ol' mis-sizing of the caches.
> I have a patch now that ends like this; if all else fails at least it'd
> not spin forever, and give a hint of what to try.
> Phase 6 - check inode connectivity...
> - resetting contents of realtime bitmap and summary inodes
> - traversing filesystem ...
> unknown magic number 0 for block 8388608 in directory inode 40541
> rebuilding directory inode 40541
> unknown magic number 0 for block 8388608 in directory inode 48934
> rebuilding directory inode 48934
> unknown magic number 0 for block 8388608 in directory inode 56139
> rebuilding directory inode 56139
> unknown magic number 0 for block 8388608 in directory inode 63785
> rebuilding directory inode 63785
> Unable to free any items in cache for new node; exiting.
> Try increasing the bhash and/or ihash size beyond 64
> cache: 0x190ed4d0
> Max supported entries = 512
> Max utilized entries = 512
> Active entries = 512
> Hash table size = 64
> Hits = 130779
> Misses = 271155
> Hit ratio = 32.54
I made some tests and it seems, that filesystem to finish xfs_repair
needs to be repaired with bhash=1024... With default options it still
hangs on "traversing filesystem..." Is it possible to change this
behavior to normal in other way than reformat? Moreover I spotted some
strange thing. 16GB of data has been moved to lost+found. I tried to
clean L+F by
# rm -rf lost+found
but suddenly I got this:
# ls -l /mnt/storage/
ls: cannot access /mnt/storage/lost+found: No such file or directory
drwxr-xr-x 4 root root 33 Mar 4 17:21 l_mirror
?????????? ? ? ? ? ? lost+found
I had to run xfs_repair (bhash=1024) once again and then l+f disappeared...
So I started to think: does it have some influence on data that are
stored on this filesystem? I'm afraid that files on this FS may become