public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What is the most error resistant filesystem?
Date: Tue, 04 Oct 2011 00:54:42 -0400	[thread overview]
Message-ID: <4E8A9192.2010206@orlitzky.com> (raw)
In-Reply-To: <CAA2qdGWz3kunX7xKNyw8oE1wPUHVW1YjV_SpbAATy9OTCzJb5A@mail.gmail.com>

On 10/03/2011 11:47 PM, Pandu Poluan wrote:
> Hello people!
> 
> Now, I have the same question as this guy:
> 
> https://bbs.archlinux.org/viewtopic.php?id=66651
> 
> I.e., what is the most robust filesystem for Linux?
> 
> The box will be used as a gateway/firewall for a branch office, so I
> really couldn't care less about filesystem performance. But the utility
> power there is horrendous, so I need something that can shrug off a
> catastrophic power loss, and/or very fast fsck.
> 
> I'd also appreciate any tips on mount options to further enhance robustness.

Journaling filesystems are as safe as you'll get on commodity hardware.
I would choose ext4 because I'm familiar with it, but I'm sure others
offer the same options. It's also got the fastest fsck that I'm aware of.

From `man tune2fs`:

  journal_data
    When the filesystem is mounted with journalling
    enabled, all data (not just metadata) is committed into
    the journal prior to being written into the main
    filesystem.


  block_validity

    (I haven't used this, but spotted it in the man page)

    The file system will be mounted with the block_validity
    option enabled, which causes extra checks to be per‐
    formed after reading or writing from the file system.
    This prevents corrupted metadata blocks from causing
    file system damage by overwriting parts of the inode
    table or block group descriptors. This comes at the
    cost of increased memory and CPU overhead, so it is
    enabled only for debugging purposes. (This option is
    currently only supported by the ext4 file system driver
    in 2.6.35+ kernels.)





  parent reply	other threads:[~2011-10-04  4:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04  3:47 [gentoo-user] What is the most error resistant filesystem? Pandu Poluan
2011-10-04  4:25 ` Michael Mol
2011-10-04  4:34   ` Pandu Poluan
2011-10-04  4:47     ` Canek Peláez Valdés
2011-10-04  4:27 ` Hilco Wijbenga
2011-10-04  4:54 ` Michael Orlitzky [this message]
2011-10-04  5:23 ` Paul Hartman
2011-10-07 16:06   ` Diego Augusto Molina

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=4E8A9192.2010206@orlitzky.com \
    --to=michael@orlitzky.com \
    --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