From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>, Andi Kleen <ak@suse.de>,
Andreas Dilger <adilger@turbolinux.com>,
monkeyiq <monkeyiq@users.sourceforge.net>,
linux-kernel@vger.kernel.org, Nikita Danilov <god@namesys.com>
Subject: Re: Dying disk and filesystem choice.
Date: Fri, 25 May 2001 09:21:42 -0700 [thread overview]
Message-ID: <3B0E8696.5B1F304@namesys.com> (raw)
In-Reply-To: <208080000.990796886@tiny>
Chris Mason wrote:
>
> On Thursday, May 24, 2001 11:16:58 PM +0100 Alan Cox
> <alan@lxorguk.ukuu.org.uk> wrote:
>
> >> IMHO we are not that deep into code freeze anymore. Freevxfs got added
> >> in linux-2.4.5-pre*, so I think that a patch that adds a useful feature
> >> like badblock support would be OK.
> >
> > FreeVxFS changes precisely nothing in the behaviour of any other fs - its
> > like adding a new driver.
> >
> > Updating Reiserfs requires a lot more care because it has the potential to
> > harm existing stable setups
>
> This has been mostly covered, but just in case. There are two different
> freezes, the kernel, and in reiserfs. The reiserfs part isn't something
> Alan or Linus have imposed on us, we just wanted to limit the reiserfs
> changes as much as possible during the early kernel releases.
>
> The end result is that some larger scale issues are unfixed (memory
> pressure from VM, lost files after a crash), but we have been able to focus
> on the critical hoses-my-files/crashes-my-box kinds of bugs.
>
> -chris
No, our policy is strictly in sync with and reflective of that of the rest of
the linux-kernel. Since the ac series has a different policy, we can be
different in regards to the ac series.
And I don't begin to comprehend your not sending in the lost disk space after
crash bug fix (I assume it is what you mean when you refer to lost files after a
crash, because I know of no lost files after a crash bug, please phrase things
more carefully), and it really annoys me and the users, frankly. Why you
consider that a feature is beyond me.
monstr, could you fix it please and send the fix in? We can't wait for Chris to
send it in any longer.
Thx,
Hans
next prev parent reply other threads:[~2001-05-25 16:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 3:25 Dying disk and filesystem choice monkeyiq
2001-05-24 6:03 ` Hans Reiser
2001-05-24 6:58 ` Andreas Dilger
2001-05-24 8:31 ` Andi Kleen
2001-05-24 10:19 ` Jens Axboe
2001-05-24 12:08 ` monkeyiq
2001-05-24 15:46 ` Jonathan Lundell
2001-05-24 15:50 ` Jonathan Lundell
2001-05-24 15:56 ` Andi Kleen
2001-05-24 16:13 ` Jonathan Lundell
2001-05-24 16:53 ` Hans Reiser
2001-05-24 17:16 ` David Rees
2001-05-24 19:03 ` J Sloan
2001-05-24 20:54 ` Hans Reiser
2001-05-24 19:46 ` Erik Mouw
2001-05-24 21:24 ` Hans Reiser
2001-05-24 22:16 ` Alan Cox
2001-05-25 13:21 ` Chris Mason
2001-05-25 16:21 ` Hans Reiser [this message]
2001-05-25 16:58 ` Chris Mason
2001-05-25 17:42 ` Hans Reiser
2001-05-25 11:29 ` Juan Quintela
2001-05-24 21:35 ` monkeyiq
-- strict thread matches above, loose matches on Subject: below --
2001-05-24 17:30 Cress, Andrew R
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=3B0E8696.5B1F304@namesys.com \
--to=reiser@namesys.com \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=adilger@turbolinux.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=god@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=monkeyiq@users.sourceforge.net \
/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