From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.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 12:58:18 -0400 [thread overview]
Message-ID: <328640000.990809898@tiny> (raw)
In-Reply-To: <3B0E8696.5B1F304@namesys.com>
On Friday, May 25, 2001 09:21:42 AM -0700 Hans Reiser <reiser@namesys.com>
wrote:
> 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.
Not really, our policy has been much more restrictive than the rest of the
kernel. Look at the patches we didn't send in.
>
> 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.
The patch is a _huge_ change to the way files are deleted and truncated, to
what happens during mount, and to the way transactions work. It is
effectively a format extension, and must be verified against both 2.2.x
kernels and 2.4.x kernels, in both disk formats.
Before I even consider introducing a change of this size, I want to be as
sure as I can the rest of the code is stable. It is the only way we can
debug it and stay sane. Even after I release the code, I won't want it in
an ac series for a while. It does much more harm than good if it somehow
ruins compatibility with an older kernel, especially in 2.4.x.
Yes, it is a bug fix. But, it is a very different kind of bug fix than
something that corrupts files at random, or something that doesn't get
buffers to disk at the right time.
I won't pretend the fix isn't important, but I won't allow larger changes
to ruin the progress we've made so far.
-chris
next prev parent reply other threads:[~2001-05-25 17:04 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
2001-05-25 16:58 ` Chris Mason [this message]
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=328640000.990809898@tiny \
--to=mason@suse.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=monkeyiq@users.sourceforge.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