public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Hunter <sean@dev.sportingbet.com>
To: "sebastien.cabaniols" <sebastien.cabaniols@laposte.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [POT] Which journalised filesystem uses Linus Torvalds ?
Date: Wed, 3 Oct 2001 15:48:40 +0100	[thread overview]
Message-ID: <20011003154840.L30743@dev.sportingbet.com> (raw)
In-Reply-To: <GKMPCZ$IZh2dKhbICnp0WDXKHB6iO7OKoHwqOxmqj9XfriOC7PjHiIDA6bHi6xrImT@laposte.net> <E15on3F-0005DB-00@schizo.psychosis.com>
In-Reply-To: <E15on3F-0005DB-00@schizo.psychosis.com>; from dcinege@psychosis.com on Wed, Oct 03, 2001 at 10:33:17AM -0400

I use ext3 on a couple of servers and a couple of laptops.  I think which fs is
best for you will depend enormously on the intended use of the machines and
your own expectations.  A mail and dns server that I operate running ext3 has
been very happy since conversion, and has definitely benefitted.

I feel I get the benefit of no more fscks and fast operations on "-o
sync"-mounted filesystems without (IMO) exposing the box to immature code that
you might see in less conservative "experimental" filesystem options.

I personally feel more comfortable with the stability and robustness criteria
of the ext3 developers than some others.  If you want a very fast filesystem or
one that handles very large numbers of files very well, your choice may well be
different from mine.

I quite like my filesystems to be boring. :)

Sean

On Wed, Oct 03, 2001 at 10:33:17AM -0400, Dave Cinege wrote:
> On Wednesday 03 October 2001 8:00, sebastien.cabaniols wrote:
> > Hello lkml,
> >
> > 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 use Reiserfs on everything now, including a 13 drive Fiber Channel 
> SAN with 3 hosts and multiple levels of Software RAID between them.
> 
> It is as fast as ext2, and in some case much faster. (IE rm 10K+ files in ~2 
> seconds) FYI I Bonnie 70MB/s on 6 7200rpm drives in RAID 0. (64k blocks)
> 
> Keeping up with the 'best' reiserfs patch set can be a little bit of a
> chore. (However it looks like we're coming to the end of that with 2.4.10)
> 
> Never used ext3. From what I did read about it, it didn't excite me.
> The others I've yet to see a mature enough version to actually use, and 
> considering Reiserfs, don't see a reason to try them.
> 
> Dave
> 
> -- 
> The time is now 22:19 (Totalitarian)  -  http://www.ccops.org/clock.html
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

  reply	other threads:[~2001-10-03 14:48 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 [this message]
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
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=20011003154840.L30743@dev.sportingbet.com \
    --to=sean@dev.sportingbet.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