public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: amd64 installation: which file system?
Date: Thu, 20 Jul 2006 11:14:41 -0700	[thread overview]
Message-ID: <7573e9640607201114o624b56ddhf7eeb1cd5ee5b40d@mail.gmail.com> (raw)
In-Reply-To: <1153393308.3839.123.camel@devilbox>

On 7/20/06, Cliff Wells <cliff@develix.com> wrote:
> As a more useful bit of info than anecdotes and scaremongering, here's a
> decent article that covers XFS in fair detail and compares a few of its
> major differences from the other journaled filesystems:
>
> http://www-128.ibm.com/developerworks/library/l-fs9.html

Posting links to articles written by Gentoo's founder is cheating! :-)

But in fact, Daniel didn't really address the real-world reliability
of the filesystems.  He addressed it theoretically, and only in
relation to reiserfs, not ext3.  But in fact I disagree with one
assertion that Daniel makes:

"but writing metadata more frequently does encourage data to be
written more frequently as well"

In it's default configuration, XFS avoids writing data out to disk
until it absolutely has to, or a *significant* amount of time has
elapsed.  Only by tweaking /proc settings have I gotten it to flush
out data in a reasonable amount of time.

Are you seriously telling me that in all the years you have run XFS
filesystems, you have never seen /var/log/messages get padded with
nuls?  That is the kind of "corruption" that XFS is well known for.
(BTW, I _know_ this is a security feature.  But the fact is that ext3
users pretty much _never_ see this kind of data, um, "security").  It
may be great at maintaining it's own consistency, but it seems
particularly predatory to the files contained within it.  I've already
mentioned a recent corruption I had with XFS on one of my systems...

Besides, every time this discussion has come up here, the majority of
particpants have agreed that ext3 is the least likely to corrupt data.

Don't get me wrong.  I like XFS, and I am running it on my laptop and
desktop systems.  However I have tweaked the settings so that it
behaves like I want, and am very cautious about just hitting the
reset/power button when I get a lockup.  I have learned that the hard
way.

And my "bottom line" is: if someone came here and asked "what is the
most reliable filesystem", my answer would be ext3.  Hands down.

-Richard
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-20 18:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 17:48 [gentoo-user] amd64 installation questions James
     [not found] ` <loom.20060718T232824-746@post.gmane.org>
2006-07-18 22:01   ` [gentoo-user] Re: amd64 installation: which file system? Richard Fish
2006-07-18 22:12     ` James
2006-07-18 23:31       ` Neil Bothwick
2006-07-18 23:38       ` Richard Fish
2006-07-19  0:25         ` Dale
     [not found]           ` <44BD7DCA.2060903@gentoo.org>
2006-07-19  0:57             ` Richard Fish
2006-07-19  7:56               ` Mick
2006-07-19  8:23                 ` Richard Fish
2006-07-19 10:08                   ` Mick
2006-07-19  1:13             ` Cliff Wells
2006-07-19  1:32               ` Donnie Berkholz
2006-07-19  2:20                 ` Alan E. Davis
2006-07-19 10:44                 ` Neil Bothwick
2006-07-20 10:37                 ` Cliff Wells
2006-07-20 11:01                   ` Cliff Wells
2006-07-20 18:14                     ` Richard Fish [this message]
     [not found]                       ` <1153427464.3839.155.camel@devilbox>
2006-07-20 21:53                         ` Richard Fish
2006-07-19  1:21             ` Dale
2006-07-19  1:26         ` James
2006-07-19  2:57           ` Richard Fish
2006-07-19  4:31             ` James
2006-07-19  7:14               ` Mick
2006-07-29 13:30                 ` Bo Ørsted Andresen
2006-07-29 13:18         ` Bo Ørsted Andresen

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=7573e9640607201114o624b56ddhf7eeb1cd5ee5b40d@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@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