public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wendall Cada <wendallc@83864.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] what is the best filesystem for a server
Date: Tue, 20 May 2008 20:34:02 -0700	[thread overview]
Message-ID: <4833982A.7010407@83864.com> (raw)
In-Reply-To: <200805210029.52385.oliver.schad@oschad.de>

Oliver Schad wrote:
> Am Mittwoch, 21. Mai 2008 schrieb mir Edward Muller:
>   
>> reiserfs, purely from the recovery angle.
>>     
>
> Yeah, if you have fuck up in the B-Trees, it's the best filesystem purely from 
> the rubbish heap's angle.
>
> regards
> Oli
>   

Oli is correct. If reiser dies, the data is completely lost. It writes 
to the journal first, then writes the data. That, and when it decides to 
completely kill your B-Trees, you're screwed. After three unrecoverable 
reiserfs issues, I moved over to ext3 and have been very happy.

I personally think the speed differences on most production servers is 
negligible. At the end of the day, I'd much rather have my data intact 
than have it be X% faster in certain situations. Also, ext3 has quite a 
few configuration options to optimize for your particular needs. See 
/etc/mke2fs.conf for some example configurations. The main problem 
you'll have with ext3 is that you cannot change to things like the block 
size or number of inodes on-the-fly like you can with xfs. So make sure 
what you format with will suit your needs. The one other major strength 
of ext3 is that it is able to change to ext2 or ext4 without 
reformatting the partition. You cannot do this with reiser or any of the 
others. reiserfs3 is not compatible with reiserfs4 for example.

And I've got to think that the NTFS comment was entirely sarcasm.

Wendall
-- 
gentoo-server@lists.gentoo.org mailing list



  reply	other threads:[~2008-05-21  3:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19  2:41 [gentoo-server] what is the best filesystem for a server widyachacra
2008-05-19  3:02 ` deface
2008-05-19  3:07 ` Aaron Clark
2008-05-20 11:47 ` Tomasz Lutelmowski
2008-05-20 21:29   ` Gunnar Mann
2008-05-20 22:02   ` Thilo Bangert
2008-05-20 22:06     ` gregorcy
2008-05-20 22:25 ` Edward Muller
2008-05-20 22:29   ` Oliver Schad
2008-05-21  3:34     ` Wendall Cada [this message]
2008-05-24 16:22       ` A. Khattri
2008-05-24 17:23         ` RijilV
2008-05-24 17:40           ` Michelangelo
2008-06-06 13:18             ` A. Khattri
2008-06-09  9:28               ` "Todd M. Hébert"
2008-06-09 16:01                 ` RijilV
2008-06-09 16:29                   ` "Todd M. Hébert"
2008-06-10  2:41                     ` JD Gray
2008-06-10  8:23                       ` "Todd M. Hébert"
2008-06-09 17:10               ` kashani
2008-05-21  6:15 ` Christian Bricart

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=4833982A.7010407@83864.com \
    --to=wendallc@83864.com \
    --cc=gentoo-server@lists.gentoo.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