From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
Cc: kernel@Expansa.sns.it,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: XFS in the main kernel
Date: Tue, 23 Apr 2002 17:47:02 +0200 [thread overview]
Message-ID: <3CC581F6.6050103@loewe-komp.de> (raw)
In-Reply-To: <3CC56355.E5086E46@TeraPort.de>
Martin Knoblauch wrote:
>>Re: XFS in the main kernel
>>
>>From: Luigi Genoni (kernel@Expansa.sns.it)
>>On Tue, 23 Apr 2002, Keith Owens wrote:
>>
>>
>>>On 22 Apr 2002 18:55:20 +0200,
>>>wichert@cistron.nl (Wichert Akkerman) wrote:
>>>
>>>>In article <3CC427F4.12C40426@fnal.gov>,
>>>>Dan Yocum <yocum@fnal.gov> wrote:
>>>>
>>>>>I know it's been discussed to death, but I am making a formal request to you
>>>>>to include XFS in the main kernel. We (The Sloan Digital Sky Survey) and
>>>>>many, many other groups here at Fermilab would be very happy to have this in
>>>>>the main tree.
>>>>>
>>>>Has XFS been proven to be completely stable
>>>>
>>>As much as any other filesystem. "There are no bugs in filesystem XYZ.
>>>That just means that you have not looked hard enough." :) There is a
>>>daily QA suite that XFS is run through.
>>>
>>In the reality the inclusion on XFS in the 2.5 tree would probably move
>>more peole to use it, and so also to eventually trigger bugs, to report
>>them, sometimes to fix them.
>>This way XFS would improve faster, and of course that would be a
>>good thing.
>>
>>
>
> definitely. Unless XFS is in the mainline kernel (marked as
> experimantal if necessary) it will not get good exposure.
>
> The most important (only) reason I do not use it (and recommend our
> customers against using it) is that at the moment it is impossible to
> track both the kernel and XFS at the same time. This is a shame, because
> I think that for some application XFS is superior to the other
> alternatives (can be said about the other alternatives to :-).
>
>
>>That said, it is important to
>>consider the technical reasons to include XFS in 2.5 or not; if this
>>inclusion could cause some troubles, if XFS fits the requirements
>>Linus asks for the inclusion and what impact the inclusion would have on
>>the kernel (Think to JFS as a good example of an easy inclusion, with low
>>impact).
>>
>>
>
> so, what were the main obstacles again? The VFS layer?
>
The VFS and such features like "delayed block allocation". XFS tries
to gather 64K or so before submitting to disk/block layer.
FWIW, SuSE 8 ships with full (but experimental marked) XFS support.
next prev parent reply other threads:[~2002-04-23 15:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 13:36 XFS in the main kernel Martin Knoblauch
2002-04-23 14:30 ` Stephen Lord
2002-04-23 15:47 ` Martin Knoblauch
2002-04-23 21:37 ` J.A. Magallon
2002-04-23 9:23 ` Daniel Phillips
2002-04-24 9:32 ` Luigi Genoni
2002-04-23 15:47 ` Peter Wächtler [this message]
2002-04-23 15:55 ` Martin Knoblauch
2002-04-23 21:43 ` Luigi Genoni
2002-04-23 9:32 ` Daniel Phillips
2002-04-24 7:13 ` Martin Knoblauch
2002-04-24 9:02 ` Luigi Genoni
[not found] <20020422234419.GQ2470@dstl.gov.uk>
2002-04-23 8:31 ` Tony Gale
-- strict thread matches above, loose matches on Subject: below --
2002-04-22 15:10 Dan Yocum
2002-04-21 15:29 ` Daniel Phillips
2002-04-22 16:55 ` Wichert Akkerman
2002-04-22 22:19 ` Matthias Andree
2002-04-22 22:47 ` Chris Mason
2002-04-22 23:29 ` Keith Owens
2002-04-22 23:44 ` Wichert Akkerman
2002-04-23 0:43 ` Luigi Genoni
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=3CC581F6.6050103@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=Martin.Knoblauch@TeraPort.de \
--cc=kernel@Expansa.sns.it \
--cc=linux-kernel@vger.kernel.org \
/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