public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>,
	Alexander Zarochentcev <zam@namesys.com>
Subject: Re: [reiserfs-list] Re: Apparent instability of reiserfs on 2.4.1
Date: Tue, 13 Feb 2001 01:39:02 +0300	[thread overview]
Message-ID: <3A886606.E3557ED3@namesys.com> (raw)
In-Reply-To: <386960000.982019012@tiny>

Chris Mason wrote:
> 
> On Monday, February 12, 2001 11:42:38 PM +0300 Hans Reiser
> <reiser@namesys.com> wrote:
> 
> >> Chris,
> >>
> >> Do you know if the people reporting the corruption with reiserfs on
> >> 2.4 were using IDE drives with PIO mode and IDE multicount turned on?
> >>
> >> If so, it may be caused by the problem fixed by Russell King on
> >> 2.4.2-pre2.
> >>
> >> Without his fix, I was able to corrupt ext2 while using PIO+multicount
> >> very very easily.
> >
> 
> I suspect the bugfixes in pre2 will fix some of the more exotic corruption
> reports we've seen, but this one (nulls in log files) probably isn't caused
> by a random (or semi-random) lower layer corruption.  These users are not
> seeing random metadata corruption, so I suspect this bug is different (and
> reiserfs specific).
> 
> > Was the bug you describe also present in the 2.2.* series?  If not, then
> > the bugs are not the same.
> >
> 
> In 2.2 code the only data file corruption I know if is caused by a crash....
> 
> -chris

Chris, your quoting is very confusing above..... but I get your very interesting
remark (thanks for noticing) that the nulls are specific to crashes on 2.2, and
therefor could be due to the elevator bug on 2.4.  It even makes rough sense
that the elevator bug (said to occasionally cause a premature write of the wrong
buffer) could cause an effect similar to a crash.  I hope it is true, let's ask
all users to upgrade to pre2 (a good idea anyway) and see if it cures.

zam is perhaps very clever for deferring working on this bug......:-)

Hans
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://vger.kernel.org/lkml/

  reply	other threads:[~2001-02-12 23:12 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07 12:06 Apparent instability of reiserfs on 2.4.1 Hans Reiser
2001-02-07 15:47 ` Chris Mason
2001-02-07 16:38   ` [reiserfs-list] " David Rees
2001-02-07 16:48     ` Chris Mason
2001-02-08  6:34       ` Daniel Stone
2001-02-10 13:02         ` Chris Wedgwood
2001-02-10 13:05           ` Daniel Stone
2001-02-10 13:08             ` Chris Wedgwood
2001-02-11  7:00             ` Hans Reiser
2001-02-12  0:56               ` Chris Mason
2001-02-12 19:11                 ` Marcelo Tosatti
2001-02-12 20:42                   ` Hans Reiser
2001-02-12 19:33                     ` Marcelo Tosatti
2001-02-12 21:01                       ` Hans Reiser
2001-02-12 23:03                     ` Chris Mason
2001-02-12 22:39                       ` Hans Reiser [this message]
2001-02-13  0:18                         ` Chris Mason
2001-02-12 22:44                       ` Hans Reiser
2001-02-11  6:58           ` Hans Reiser
2001-02-10 14:47         ` Alan Cox
2001-02-10 21:16           ` David Ford
2001-02-11  0:36             ` Andrius Adomaitis
2001-02-11  8:29             ` Hans Reiser
     [not found]               ` <wvu261oa80.fsf@freeze.oslo.dnmi.no>
2001-02-11  8:59                 ` Hans Reiser
2001-02-11  9:52                   ` Adrian Phillips
2001-02-11  9:47                     ` Hans Reiser
2001-02-11 17:10                       ` Alan Cox
2001-02-11 19:56                         ` Andi Kleen
2001-02-12  2:17                           ` Rogerio Brito
2001-02-12  9:49                             ` Andi Kleen
2001-02-12 13:39                           ` Henning P. Schmiedehausen
2001-02-11 21:16                         ` Hans Reiser
2001-02-12  9:36                           ` Alan Cox
2001-02-11 10:53             ` Alan Cox
2001-02-11  8:50           ` Hans Reiser
     [not found]     ` <3A818619.7C3967BC@baldauf.org>
2001-02-07 17:39       ` Chris Mason
2001-02-07 17:53         ` Xuan Baldauf
2001-02-07 19:14         ` Xuan Baldauf
2001-02-07 21:47       ` Chris Wedgwood
2001-02-07 21:55         ` Chris Mason
2001-02-07 22:05           ` Xuan Baldauf
2001-02-07 22:13             ` Chris Mason
2001-02-07 18:41   ` Vedran Rodic
2001-02-07 18:45     ` Chris Mason
2001-02-07 19:15       ` Ivan Pulleyn

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=3A886606.E3557ED3@namesys.com \
    --to=reiser@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mason@suse.com \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@namesys.com \
    /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