I have a large filesystem (14 TB) which suffered a RAID failure which seems to have corrupted some inodes. Unfortunately as a result there are now a number of inodes with "false extents" which result in a very large number of multiply claimed blocks. I have tried to run e2fsck on this filesystem, and it gets as far as phase 1D, at which point it starts running at a glacial pace. After 48 hours -- most of it sitting at 100% CPU executing no system calls at all -- it claims to have processed a single file out of almost 10000. Anything I can do (to rescue the filesystem or try to debug the problem) other than "wipe and start over"? I believe this is e2fsck 1.42.3 from Fedora 17. -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
