Hello, yesterday i was forced to start a fsck of an ext4 filesystem (4 TB on a encrypted raid5 array). After a while a got a lot of those messages: Inode 23565579 should not have EOFBLOCKS_FL set (size 0, lblk -1) After some googling i found this thread http://kerneltrap.org/mailarchive/linux-ext4/2010/8/19/6885408/thread#mid-6885408 Since it's something that can be taken care of by using "-p" i started it yesterday and was kind of surprised to discover it running happily today with no sign of stopping. I piped the output to /dev/null since the printing of the messages alone caused quite a bit of load so i don't know at which inode fsck currently is. Is there a way to speed things up? If i understand the thread correctly those errors should self correct over time and i don't want to wait anymore. Can i do any harm by killing fsck and start it again without the pipe to see at which inode it currently is? Bye, Johannes -- 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
