Hello! I have a little problem with XFS filesystem that I have on one of my machines. I try to make xfs_repair that was not making any problems before, but xfs_repair stops on: Phase 6 - check inode
... You might try running with -P, though I doubt that's the issue. If that doesn't help, you could provide an xfs_metadump image (in public or to me in private) and I'll take a look to see what's go
Thank you! I will just left xfs_repair -P to do the job and let you know if it helps. Otherwise, I'll send you metadump image in private. Best regards, Tomasz Kruszona
No fix for you yet, but it's in cache_node_get(), in the for(;;) loop, and it looks like cache_node_allocate() fails to get a new node and we keep spinning. I need to look some more at what's going o
Hello! Is this specific behavior for this particular broken filesystem or is it a bug in functions you mentioned? I'm just curious :) Best regards, Tomasz Kruszona
This looks like some of the caching that xfs_repair does is mis-sized, and it gets stuck when it's unable to find a slot for a new node to cache. IMHO that's still a bug that I'd like to work out. If
Is it safe to use xfs_repair without this options after the FS was repaired? Or maybe I should use them every time I have similar problem? It doesn't matter. On this filesystem is a lot of small file
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
[snip] 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
... It has nothing to do w/ the format, it's just internal to xfs_repair while it's running, the way it caches blocks that it has recently used. Yeah ... huh. let me try on the repaired metadata imag