public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michelangelo <michelangelo.bottura@gmail.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] what is the best filesystem for a server
Date: Sat, 24 May 2008 19:40:59 +0200	[thread overview]
Message-ID: <23a5d5f00805241040h3563d04iaf38827ba4194bee@mail.gmail.com> (raw)
In-Reply-To: <41195fb10805241023v7829e298l9e124809bedf7aeb@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]

Summing it up, IMHO.

- NTFS is not a choice, really, you wanna stay in linux land. Besides, you
would have to find some tool|workaround for defragmenting it :/
- reiserfs is not that manageable: as others said, it does not allow
recovery from filesystem damage (let alone from hd failure). Reiserfs4
promised a breakthru, but right now is not ready to be used.
- ext3 has got decent performance for general purpose servers as well as
desktop boxes, and you can find lot of recovery tools (even some win32
ones), so this is my main choice
- go XFS on "big" servers with all the standard redundant hw equipment, but
only if you foresee heavy filesystem workload



Besides, RAID 5 is not always a good choice: I got 2 adaptec and 3ware cards
that got them bioses/nvram messed up thanks to power spikes during the big
italian blackout back in 2003. And yes, they were behind  online APC ups
Mic

On Sat, May 24, 2008 at 7:23 PM, RijilV <rijilv@gmail.com> wrote:

> 2008/5/24 A. Khattri <ajai@bway.net>:
> > Technical arguments aside, if you're serious about data loss and/or
> > performance, you would be using hardware RAID anyway. 3ware cards are
> pretty
> > cheap and the extra money is well worth it for peace of mind.
>
>
> +1 for 3ware.
>
> Also, the initial problem with this thread is that there were no
> requirements listed.  What's the best file system largely depends on
> what you're doing.  If its a IMAP server VS an Oracle database, you'd
> pick two entirely different filesystems.
>
> Asking a what the best filesystem is without any qualifications or
> requirements doesn't give you a very good answer, more likely you're
> going to get which filesystem has the most fans.
>
> .r'
> --
> gentoo-server@lists.gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 2321 bytes --]

  reply	other threads:[~2008-05-24 17:41 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
2008-05-24 16:22       ` A. Khattri
2008-05-24 17:23         ` RijilV
2008-05-24 17:40           ` Michelangelo [this message]
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=23a5d5f00805241040h3563d04iaf38827ba4194bee@mail.gmail.com \
    --to=michelangelo.bottura@gmail.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