Re: ext2 FS Corruption

Richard B. Johnson (root@chaos.analogic.com)
Fri, 19 Jun 1998 08:26:38 -0400 (EDT)


On Fri, 19 Jun 1998, Ganesh Sittampalam wrote:

> On Thu, 18 Jun 1998 16:42:35 -0400 (EDT), you wrote:
>
> >[SNIPPED]
> >>
> >> Oh well. I asked because the line "Deleted inode 10413 has zero dtime." always
> >> indicated a dynamic init for me. BTW, is it always inode 10413?
> >>
> >Nope. And there's more that just a zero dtime also.
>
> How many people besides you can reproduce this corruption on definitely reliable
> hardware? After my first report I have been unable to reproduce it at all, which
> means that the damage could have happened on any one of many previous proper
> unmounts, under a variety of kernels.
>
> I'll keep trying to get it to happen again.

Lots of people so far. At first some would just do a fsck and report
that everything was fine. They didn't realilize you have to do a
fsck -f to force a real file-system check.

Cheers,
Dick Johnson
***** FILE SYSTEM MODIFIED *****
Penguin : Linux version 2.1.105 on an i586 machine (66.15 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu