On 03/06/2011 07:25 PM, Alex Schuster wrote:
Nikos Chantziaras writes:
Before leaving home, I started an fsck.ext4 on a filesystem (500GB) that
resides on a disk that I suspect is damaged:
fsck.ext4 -c -c -f /dev/sdb1
When I came back 10 hours later, it was still checking. After 2 hours
more (so it took 12 hours total) it finally finished. The output was
Anything about erros in dmesg or syslog?
Nope. All clean.
[...]
Were there any bad blocks or not? Is
there a way to query the filesystem for the now known bad blocks? (The
"Updating bad block inode." message suggests that such a list is stored
directly inside the filesystem.)
dumpe2fs -b /dev/sdb1 probably also works for ext4.
Thanks. I just tried and it prints nothing. I guess that means no bad
blocks were found.
(Rant: Don't you just love programs that instead of explicitly telling
you that all is OK, they just stay silent, leaving you wondering whether
they actually work at all? Argh...)
