From: Oleg Drokin <green@namesys.com>
To: Luigi Genoni <kernel@Expansa.sns.it>
Cc: Alex Riesen <fork0@users.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [reiserfs-dev] 2.5.4-pre1: zero-filled files reiserfs
Date: Thu, 14 Feb 2002 08:50:59 +0300 [thread overview]
Message-ID: <20020214085059.B5605@namesys.com> (raw)
In-Reply-To: <20020213160851.A894@namesys.com> <Pine.LNX.4.44.0202131811090.21799-100000@Expansa.sns.it>
In-Reply-To: <Pine.LNX.4.44.0202131811090.21799-100000@Expansa.sns.it>
Hello!
On Wed, Feb 13, 2002 at 06:15:24PM +0100, Luigi Genoni wrote:
> 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.
There was a bug in kernels up to 2.5.4-pre1 (2.5.4-pre2 had a fix),
which had similar symtoms.
> > > 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..
Great.
Thing is if you able to reproduce on 2.5.4-pre2+ without rebooting into earlier
2.5 kernels in-between tries, then it will mean something is not right even
in latest kernels.
Bye,
Oleg
next prev parent reply other threads:[~2002-02-14 5:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 7:23 2.5.4-pre1: zero-filled files resiserfs Alex Riesen
2002-02-07 7:44 ` [reiserfs-dev] " Oleg Drokin
2002-02-07 22:02 ` Alex Riesen
2002-02-08 5:51 ` Oleg Drokin
2002-02-08 6:34 ` Oleg Drokin
2002-02-08 22:07 ` [reiserfs-dev] 2.5.4-pre1: zero-filled files reiserfs Alex Riesen
2002-02-11 5:51 ` Oleg Drokin
[not found] ` <Pine.LNX.4.44.0202111247270.21009-100000@Expansa.sns.it>
2002-02-11 12:17 ` Alex Riesen
2002-02-11 13:09 ` Oleg Drokin
[not found] ` <20020211141422.A16832@steel>
[not found] ` <20020211162743.A1282@namesys.com>
2002-02-11 14:03 ` Alex Riesen
2002-02-11 14:23 ` Luigi Genoni
2002-02-11 14:27 ` Oleg Drokin
2002-02-11 19:19 ` Luigi Genoni
2002-02-12 16:55 ` Luigi Genoni
2002-02-12 17:01 ` Oleg Drokin
2002-02-12 17:13 ` Luigi Genoni
2002-02-13 5:56 ` Oleg Drokin
2002-02-13 11:11 ` Luigi Genoni
2002-02-13 13:08 ` Oleg Drokin
2002-02-13 17:15 ` Luigi Genoni
2002-02-14 5:50 ` Oleg Drokin [this message]
2002-02-14 9:57 ` reiserfs oops with 2.5.5-pre1 (was: [reiserfs-dev] 2.5.4-pre1:)zero-filled " Luigi Genoni
2002-02-14 10:01 ` Oleg Drokin
2002-02-13 20:01 ` [reiserfs-dev] 2.5.4-pre1: zero-filled " Alex Riesen
2002-02-14 5:46 ` Oleg Drokin
2002-02-12 19:33 ` Alex Riesen
2002-02-11 14:20 ` Luigi Genoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020214085059.B5605@namesys.com \
--to=green@namesys.com \
--cc=fork0@users.sourceforge.net \
--cc=kernel@Expansa.sns.it \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox