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.)
