> Date: Thu, 21 May 1998 12:41:12 -0400
> From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
> To: hpa@transmeta.com, trevor@jpj.net
> Cc: linux-kernel@vger.rutgers.edu
> Subject: Re: FW: Corrupted filesystem
>
>
> I thought had responded to Trevor personally earlier (Trevor, my
> apologies if somehow you didn't get my note, if that's why you then sent
> mail to linux-kernel).
>
> >From his description, it seemed pretty clear that something had
> scribbled over the beginning of the inode table, which is why there was
> trash in inode #5, and large number of inodes were in /lost+found.
>
> If this happened purely because of an unclean shutdown (which is what I
> believe he said), then there was something really strange happening with
> his hardware indeed, since disks should scribble over random places on
> the disk, even if they get powered down in the middle of a write
> request.....
>
> - Ted
I did not see the original message, but I have seen the effect of a
trashed inode table twice before (due to faulty hardware on both
occations)
On one occation the drive power supply was loose leading to horrific
corruption and bad sectors.
The second occation was due to a faulty IDE controler (or possibly DMA
controler etc) which caused serious corruption when both IDE channels were
used at the same time. This caused my inode table to be destroyed on a
regular basis when my machine started swapping to the second disk (the
writes were due to inode atime updates) :( I soon learned the wisdom of a
read only root partition, and backups !
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu