From: Pavel Machek <pavel@suse.cz>
To: Hans Reiser <reiser@namesys.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Daniel Phillips <phillips@bonn-fries.net>,
Andrew Morton <akpm@zip.com.au>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] delayed disk block allocation
Date: Wed, 6 Mar 2002 12:59:01 +0000 [thread overview]
Message-ID: <20020306125900.B81@toy.ucw.cz> (raw)
In-Reply-To: <3C7F3B4A.41DB7754@zip.com.au> <E16hhuI-0000S6-00@starship.berlin> <20020304050450.GF353@matchmail.com> <20020303223103.J4188@lynx.adilger.int> <3C8308FE.FC4FA42@mandrakesoft.com> <20020303231851.N4188@lynx.adilger.int> <3C838C89.5060602@namesys.com>
In-Reply-To: <3C838C89.5060602@namesys.com>; from reiser@namesys.com on Mon, Mar 04, 2002 at 06:02:33PM +0300
Hi!
> ReiserFS V3 is pretty stable right now. Fsck is usually the last thing
> to stabilize for a filesystem, and we were no exception to that rule.
>
> ReiserFS V3 will last for probably another 3 years (though it will
> remain supported for I imagine at least a decade, maybe more), with V4
> gradually edging it out of the market as V4 gets more and more stable.
> During at least the next year we will keep some staff adding minor
> tweaks to V3. For instance, our layout policies will improve over the
> next few months, journal relocation is about to move from Linux 2.5 to
> 2.4, and data write ordering code is being developed by Chris. I don't
> know how long fsck maintenance for V3 will continue, but it will be at
> least as long as users find bugs in it.
When you think youer fsck works, let me know. I have some tests to find
bugs in fsck....
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-03-07 20:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 8:26 Andrew Morton
2002-03-04 2:08 ` Daniel Phillips
2002-03-04 3:10 ` Jeff Garzik
2002-03-04 7:27 ` Andrew Morton
2002-03-04 5:04 ` Mike Fedyk
2002-03-04 5:31 ` Andreas Dilger
2002-03-04 5:40 ` Mike Fedyk
2002-03-04 6:14 ` Andreas Dilger
2002-03-04 5:41 ` Jeff Garzik
2002-03-04 6:18 ` Andreas Dilger
2002-03-04 15:02 ` Hans Reiser
2002-03-06 12:59 ` Pavel Machek [this message]
2002-03-04 7:53 ` Andrew Morton
2002-03-04 8:06 ` Daniel Phillips
2002-03-04 8:34 ` Andrew Morton
2002-03-04 7:20 ` Andrew Morton
2002-03-04 9:23 ` Daniel Phillips
2002-03-04 14:54 rwhron
2002-03-04 15:10 ` Jeff Garzik
2002-03-07 12:06 Etienne Lorrain
2002-03-07 14:47 ` Steve Lord
2002-03-07 17:30 ` Mike Fedyk
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=20020306125900.B81@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=reiser@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
all inboxes | Powered by JetHome®