On Wed, Apr 15, 2015 at 11:18:18AM -0400, Akos Csete wrote: > I ran into a very long execution time, approaching 48 hours, with > e2fsck 1.42.9 when running e2fsck -fyv on a 7.8TB volume after > fsck.ext4 -nf found 1761 inodes containing multiply-claimed blocks. > I've been tailing the e2fsck output combined with a timestamp and > found progress is extremely slow. > Is this slow processing expected? I checked Ted's response to a 2009 > posting for ext3 with a similar issue where he recommended selectively > wiping inodes with debugfs clri then restoring files as needed. Are > there any other options for ext4, perhaps other/faster repair > alternatives? Unfortunately, the multiple-blocks cleaner runs one block at a time and is quite slow. 1.42.12 might improve things somewhat since I cleaned out some of the stranger things it would do, but it's still not fast. (Some day in the future maybe we'll support reflink in which case this whole part of fsck can go away.) --D > > Thanks, > Akos > -- > 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 -- 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
