1 |
Am 06.03.2011 18:07, schrieb Nikos Chantziaras: |
2 |
> Before leaving home, I started an fsck.ext4 on a filesystem (500GB) that |
3 |
> resides on a disk that I suspect is damaged: |
4 |
> |
5 |
> fsck.ext4 -c -c -f /dev/sdb1 |
6 |
> |
7 |
> When I came back 10 hours later, it was still checking. After 2 hours |
8 |
> more (so it took 12 hours total) it finally finished. The output was: |
9 |
> |
10 |
> e2fsck 1.41.14 (22-Dec-2010) |
11 |
> Checking for bad blocks (non-destructive read-write test) |
12 |
> Testing with random pattern: done |
13 |
> Extra: Updating bad block inode. |
14 |
> Pass 1: Checking inodes, blocks, and sizes |
15 |
> Pass 2: Checking directory structure |
16 |
> Pass 3: Checking directory connectivity |
17 |
> Pass 4: Checking reference counts |
18 |
> Pass 5: Checking group summary information |
19 |
> |
20 |
> Extra: ***** FILE SYSTEM WAS MODIFIED ***** |
21 |
> Extra: 11/30531584 files (0.0% non-contiguous), |
22 |
> 1966902/122096638 blocks |
23 |
> |
24 |
> I'm not sure how to read this. Were there any bad blocks or not? Is |
25 |
> there a way to query the filesystem for the now known bad blocks? (The |
26 |
> "Updating bad block inode." message suggests that such a list is stored |
27 |
> directly inside the filesystem.) |
28 |
> |
29 |
> |
30 |
|
31 |
When there is nothing else reported, there was no error. "FILE SYSTEM |
32 |
WAS MODIFIED" usually just means that a directory "lost+found" was created. |