> >
> > Are other people seeing 2.1.106 corrupting disks and memory on x86 ?
> >
> > Alan
>
> This is an example after 2 days of running: I frequently do this, and
> this is a good one. After 6 - 8 days I typically have 10 - 20 inodes
> with zero dtime. My root FS is the worst affected, but then it get's
> the most reading/writing attention. There is another error that is
> wuite freqent, but I can't recall it. (I just got this after reading
> your message and trying it out on my root filesystem.
On that note, I must add the anecdote that I recall seeing the periodic
fsck come up with "Deleted inode with zero dtime" on filesystems that
otherwise should have been fine -- with Linux >= 2.0.33 (_perhaps_ >=
2.0.27, but I can't swear to it.) I don't have any logs of this, and I
assumed it was something of little importance.
> ..[snip]..
> Parallelizing fsck version 1.10 (24-Apr-97)
> e2fsck 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
> Pass 1: Checking inodes, blocks, and sizes
> Deleted inode 14510 has zero dtime. Fix<y>? yes
>
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> Fix summary information<y>? yes
>
> Block bitmap differences: -60618 -60619 -60620 -60621 -60622 -60623
> -60624
> -60625 -60626 -60627 -60628 -60629. FIXED
> Free blocks count wrong for group 7 (1183, counted=1195). FIXED
> Free blocks count wrong (214664, counted=214676). FIXED
> Inode bitmap differences: -14510. FIXED
> Free inodes count wrong for group #7 (1805, counted=1806). FIXED
> Free inodes count wrong (221839, counted=221840). FIXED
>
> /dev/hda1: ***** FILE SYSTEM WAS MODIFIED *****
> /dev/hda1: 45400/267240 files (3.7% non-contiguous), 850748/1065424
> blocks
> ..[snip]..
>
> thx..js
-- Kenneth Albanowski (kjahds@kjahds.com, CIS: 70705,126)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu