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