Am 06.03.2011 18:07, schrieb Nikos Chantziaras: > 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: > > e2fsck 1.41.14 (22-Dec-2010) > Checking for bad blocks (non-destructive read-write test) > Testing with random pattern: done > Extra: Updating bad block inode. > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > > Extra: ***** FILE SYSTEM WAS MODIFIED ***** > Extra: 11/30531584 files (0.0% non-contiguous), > 1966902/122096638 blocks > > I'm not sure how to read this. 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.) > >
When there is nothing else reported, there was no error. "FILE SYSTEM WAS MODIFIED" usually just means that a directory "lost+found" was created.
signature.asc
Description: OpenPGP digital signature
