From: Hans Reiser <reiser@namesys.com>
To: "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>,
Chris Mason <mason@suse.com>,
"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: Apparent instability of reiserfs on 2.4.1
Date: Wed, 07 Feb 2001 15:06:59 +0300 [thread overview]
Message-ID: <3A813A63.EBD1B768@namesys.com> (raw)
I know that our number of users has increased, but I doubt that the increase is
sufficient to match the marked increase in bug reports on reiserfs-list. Please
be patient as we work on this. We will issue a patch this week that will fix
some bugs (NFS i_generation count losing, and space leakage on crash due to
preallocated blocks being lost).
We will also change the default for mkreiserfs to creating the new 2.4 only
format, as this (we have belatedly realized) is probably the cause of many users
reporting they can't create large files.
We have a bug affecting add_entry which we suspect is due to our rename not
being adequately atomic and leaving hidden directory entries in the filesystem,
and we are exploring how this might happen (improper journaling, we don't yet
know....) Treat this description with the usual skepticism attached to any
explanation of a bug not fixed yet, our diagnosing continues.... This is the
most worrisome bug for us stability wise. It seems ~ a user a day encounters
it.
This patch for sure also won't fix the zeros getting added to syslog files bug
which we are desperate to learn how to reproduce at our site.
Thank you for your patience.
Hans
-
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 reply other threads:[~2001-02-07 12:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 12:06 Hans Reiser [this message]
2001-02-07 15:47 ` Apparent instability of reiserfs on 2.4.1 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
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=3A813A63.EBD1B768@namesys.com \
--to=reiser@namesys.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=mason@suse.com \
--cc=monstr@namesys.com \
--cc=ragnar@bigstorage.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