> On Wed, Feb 13, 2002 at 12:11:14PM +0100, Luigi Genoni wrote:
> > > > I run slackware 8.0.49, and there was no log replaying.
> > then I do a normal reboot in 2.4.17, without any fsck,
> > there is log reply, it is a normal reboot.
My fault, I was willing to write there is NO log reply, and I wrote it
without the NO.
> Some confusion is going on.
> So do you have log replay or you do not have log replay?
> > Well, some files get corrupted.
> Ok. That's definitely bad. You said you see corruptions on two boxes, right?
> Is it as simple as boot into 2.5.4, reiserfsck (and see no errors),
> mount an fs, do something, type "reboot" and reboot into 2.5.4 again,
> and viola - here are zeroed files. Right?
It happened when I did reboot from 2.5.4-pre1 to 2.5.4, and my
/etc/rc.c/rc.local was full of 0s.
And when I did reboot from 2.5.3 to 2.5.3 on the other box and some c
source I was editing three ours before were full of 0s.
> > I saw I am not the only one with this kind of corruption, I remember at
> > less one related mail.
> There was flaky hardware on the other report. And I think Alex Riesen
> cannot reproduce zero files anymore.
Those two boxes runned from more than 1 year and no HW problems before..
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/