From: Nathan Straz <nstraz@sgi.com>
To: "sebastien.cabaniols" <sebastien.cabaniols@laposte.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [POT] Which journalised filesystem uses Linus Torvalds ?
Date: Thu, 4 Oct 2001 11:30:00 -0500 [thread overview]
Message-ID: <20011004113000.A1458@sgi.com> (raw)
In-Reply-To: <GKMPCZ$IZh2dKhbICnp0WDXKHB6iO7OKoHwqOxmqj9XfriOC7PjHiIDA6bHi6xrImT@laposte.net>
In-Reply-To: <GKMPCZ$IZh2dKhbICnp0WDXKHB6iO7OKoHwqOxmqj9XfriOC7PjHiIDA6bHi6xrImT@laposte.net>
On Wed, Oct 03, 2001 at 02:00:35PM +0200, sebastien.cabaniols wrote:
> With the availability of XFS,JFS,ext3 and ReiserFS I am a little lost
> and I don't know which one I should use for entreprise class servers.
I'd recommend reading:
http://www.mandrakeforum.com/article.php?sid=1212&lang=en
It's an article in the Mandrake forums concerning ext3, JFS, XFS, and
ReiserFS, all of which are in Mandrake 8.1.
> In terms of intergration into the kernel, functionnalities, stability
> and performance which one is the best for entreprise class servers
For enterprise stuff, I would recommend XFS based on the tools it
provides. XFS has a complete set of tools for dumping XFS, repairing a
broken file system (should it every break), and debugging should you
find something wrong with it.
--
Nate Straz nstraz@sgi.com
sgi, inc http://www.sgi.com/
Linux Test Project http://ltp.sf.net/
next prev parent reply other threads:[~2001-10-04 16:29 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 12:00 [POT] Which journalised filesystem uses Linus Torvalds ? sebastien.cabaniols
2001-10-03 12:39 ` [POT] Which journalised filesystem ? Rik van Riel
2001-10-03 12:54 ` Dave Jones
2001-10-03 13:00 ` Billy Harvey
2001-10-04 22:14 ` Alan Cox
2001-10-04 22:14 ` Dave Jones
2001-10-04 22:24 ` Alan Cox
2001-10-03 13:01 ` Ragnar Kjørstad
2001-10-03 13:24 ` Dave Jones
2001-10-03 17:51 ` Andrew Morton
2001-10-03 15:34 ` André Dahlqvist
2001-10-04 21:25 ` Alan Cox
2001-10-04 21:53 ` Alessandro Suardi
2001-10-03 17:03 ` Matthias Andree
2001-10-03 17:40 ` Sujal Shah
2001-10-03 19:13 ` Erik Mouw
2001-10-03 20:52 ` Mark Hahn
2001-10-04 22:49 ` Bernd Eckenfels
2001-10-04 23:27 ` Linus Torvalds
2001-10-04 23:55 ` Rik van Riel
2001-10-05 14:57 ` Alan Cox
2001-10-05 15:25 ` Eric W. Biederman
2001-10-05 20:25 ` Bernd Eckenfels
2001-10-05 23:41 ` Miquel van Smoorenburg
2001-10-06 8:32 ` Tonu Samuel
2001-10-06 9:16 ` Miquel van Smoorenburg
2001-10-06 16:42 ` Bernd Eckenfels
2001-10-05 22:05 ` Pavel Machek
2001-10-07 0:51 ` Eric W. Biederman
2001-10-10 17:29 ` Stephen C. Tweedie
2001-10-05 1:05 ` Mike Fedyk
2001-10-03 17:41 ` Xavier Bestel
2001-10-03 17:53 ` Matthias Andree
2001-10-03 17:36 ` Stephen C. Tweedie
2001-10-03 17:41 ` Dave Jones
2001-10-04 21:09 ` Alan Cox
2001-10-05 10:27 ` Stephen C. Tweedie
2001-10-03 14:33 ` [POT] Which journalised filesystem uses Linus Torvalds ? Dave Cinege
2001-10-03 14:48 ` Sean Hunter
2001-10-03 16:54 ` Fabbione
2001-10-03 17:52 ` Bernd Eckenfels
2001-10-03 18:01 ` Luigi Genoni
2001-10-04 5:42 ` Andrew Ip
2001-10-04 7:32 ` Constantin Loizides
2001-10-04 16:30 ` Nathan Straz [this message]
2001-10-04 17:21 ` Hristo Grigorov
-- strict thread matches above, loose matches on Subject: below --
2001-10-03 16:21 Roy Murphy
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=20011004113000.A1458@sgi.com \
--to=nstraz@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastien.cabaniols@laposte.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