Thank you for responding.
Yes that found errors, although I'm not accustomed to interpreting the
output.
xfs_repair version 5.18.0
The output of xfs_repair -nv was quite large, as was the
xfs_metadump...not sure that's indicative of something, but I've
uploaded them here:
https://drive.google.com/drive/folders/1OyQOZNsTS1w1Utx1ZfQEH-bS_Cyj8-F2?usp=sharing
There doesn't seem to be much activity once it hangs at "process newly
discovered inodes..." so it doesn't seem like just a slow repair.
Desipte there being no sign of activity, I've let it run for 24+ hours
and saw no changes..
On 11/17/22 13:48, Eric Sandeen wrote:
On 11/17/22 12:40 PM, iamdooser wrote:
Hello,
I'm not sure this is the correct forum; if not I'd appreciate guidance.
I have a Unraid machine that experienced an unmountable file system on an array disc. Running:
xfs_repair -nv /dev/md3
Did that find errors?
works, however when running
xfs_repair -v /dev/md3
it stops at "process newly discovered inodes..." and doesn't seem to be doing anything.
I've asked in the unraid forum and they've directed me to the xfs mailing list.
Appreciate any help.
Please tell us the version of xfsprogs you're using, and provide the full xfs_repair
output (with and without -n).
If it really looks like a bug, and not simply a slow repair, providing an xfs_metadump
may help us evaluate the problem further.
-Eric
