I have a server with a ~20TB xfs file system on Linux (2.6.18-92.1.22.el5) and am running xfsprogs-2.9.4-4.el5. We had a few corrupted files which I believe were due to a SCSI issue after a recent po
It'd really be great to test more recent xfsprogs first, that one is about 2 years old. You can probably grab any recent fedora src.rpm and rebuild it, and later go back to the centos version if you
Eric, Eric Sandeen wrote: Jesse Stroik wrote: I have a server with a ~20TB xfs file system on Linux (2.6.18-92.1.22.el5) and am running xfsprogs-2.9.4-4.el5. We had a few corrupted files which I beli
Bummer :) That'd be great. Perhaps you can give these a shot: http://sandeen.fedorapeople.org/test/xfsprogs-3.0.1-8.test1.x86_64.rpm http://sandeen.fedorapeople.org/test/xfsprogs-debuginfo-3.0.1-8.te
Ok, from a metadump image Jesse provided (thanks!) it's dying in here: bno = be32_to_cpu(agfl->agfl_bno[i]); printf("agfl at %p i is %d agfl_bno[i] %u bno is %u\n", agfl, i, agfl->agfl_bno[i], bno);
Ok patch sent, but now I hit: junking entry "soh " in directory inode 128 entry ".nsr" in shortform directory 128 references invalid inode 210397 junking entry ".nsr" in directory inode 128 bogus ..
Eric, Thanks for addressing the issue with xfs_repair. that's one crunchy filesystem you've got there; what happened to it? It's not entirely clear -- the JBOD and SAS controller seem to have gotten
Turns out that it runs to completion, but another run still finds corruption. And a debug build trips asserts, so I guess there are still issues. -Eric