From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>,
"Vladimir V. Saveliev" <monstr@namesys.com>,
"zag@zag.botik.ru" <zag@zag.botik.ru>,
Alexander Zarochentcev <zam@namesys.com>,
Yury Shevchuk <sizif@botik.ru>,
Vladimir Demidov <vladimir_493451@mtu-net.ru>,
Vitaly Fertman <vetal@namesys.com>,
Edward Shushkin <edward@mail.infotel.ru>,
Nikita Danilov <god@namesys.com>,
"Yury Yu. Rupasov" <yura@yura.polnet.botik.ru>,
Alexander Lyamin <flx@msu.ru>,
"Elena V. Gryaznova" <grev@uchcom.botik.ru>,
"gawain@torque.com" <gawain@torque.com>,
"ragnar@bigstorage.com" <ragnar@bigstorage.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: Apparent instability of reiserfs on 2.4.1
Date: Wed, 07 Feb 2001 10:47:09 -0500 [thread overview]
Message-ID: <420500000.981560829@tiny> (raw)
In-Reply-To: <3A813A63.EBD1B768@namesys.com>
Ok, how about we list the known bugs:
zeros in log files, apparently only between bytes 2048 and 4096 (not
reproduced yet).
preallocated block leak on crash (fix in testing)
hidden directory entry cleanup (still reproducing, very hard to hit).
knfsd (patches in testing).
oops in reiserfs_symlink, create_virtual_node (bug in redhat gcc 2.96,
fixed by downloading the update).
We've also had a few reports of other corruptions, most of which have been
traced to hardware problems. There are two where I'm not sure of the cause
yet, but the method to trigger the bug was too simple to not be a hardware
problem.
-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 15: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 [this message]
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
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=420500000.981560829@tiny \
--to=mason@suse.com \
--cc=edward@mail.infotel.ru \
--cc=flx@msu.ru \
--cc=gawain@torque.com \
--cc=god@namesys.com \
--cc=grev@uchcom.botik.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@namesys.com \
--cc=ragnar@bigstorage.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sizif@botik.ru \
--cc=vetal@namesys.com \
--cc=vladimir_493451@mtu-net.ru \
--cc=yura@yura.polnet.botik.ru \
--cc=zag@zag.botik.ru \
--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