From: Chris Mason <mason@suse.com>
To: David Rees <dbr@spoke.nols.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: [reiserfs-list] Re: Apparent instability of reiserfs on 2.4.1
Date: Wed, 07 Feb 2001 11:48:16 -0500 [thread overview]
Message-ID: <479040000.981564496@tiny> (raw)
In-Reply-To: <20010207083854.F24270@spoke.nols.com>
On Wednesday, February 07, 2001 08:38:54 AM -0800 David Rees
<dbr@spoke.nols.com> wrote:
> On Wed, Feb 07, 2001 at 10:47:09AM -0500, Chris Mason wrote:
>>
>> Ok, how about we list the known bugs:
>>
>> zeros in log files, apparently only between bytes 2048 and 4096 (not
>> reproduced yet).
>
> Could this bug be related to the reported corruption that people with
> new VIA chipsets have been also reporting on ext2? It seems similar
> because of the location of the corruption:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=98147483712620&w=2
>
> Anyway, it can't hurt to ask the bug reported if they're using a
> newer VIA chipset and see if they will upgrade their BIOS which seems
> to fix the problem.
I'd love to blame this on VIA problems, but people are seeing it on other
chipsets too ;-)
People who report this aren't seeing general corruption, just zeros in
files of specific sizes. So, it really should be a reiserfs bug.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-07 16:48 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 [this message]
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
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=479040000.981564496@tiny \
--to=mason@suse.com \
--cc=dbr@spoke.nols.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.