Re: 2TB file system
On Wed, 17 Aug 2011 07:11:12 -0500, Stan Hoeppner wrote:
> On 8/16/2011 12:30 PM, Camaleón wrote:
>
>> A single volume of 2 TiB is very big (and big file systems are more
>> prone to errors and hard to recover in the event of a corruption...
>> fsck can take... ages? :-P).
>
> I've never seen a correlation between filesystem size and probability of
> FS corruption. FS corruptions are always due to singular events, such
> as hardware failures and kernel bugs, neither of which correlate to
> filesystem size. Thus, this is a non issue.
It is a issue if your single volume is corrupted, the bigger it is the
more files can store and the more files you can lose, don't find strange
reasons for the above statement, it was just a simple equation. I don't
like partitioning so much but having a single 2 TiB volumen is nothing I
would do (without additional measures, I mean, RAID or LVM underneath).
> EXT3/4, XFS, JFS are all journaling filesystems. Thus the need to
> manually run a check will be very rare, especially in the case of XFS.
> Thus I wouldn't shy away from a single 2TB filesystem. The average XFS
> filesystem size of machines in the wild today is well over 20TB. There
> are many multi-hundred terabyte XFS filesystems in existence, and there
> exist CXFS filesystems over 1 petabyte.
ReiserFS is another journaled file system and does the fsck quite well (I
mean, fast and when it finds inconsistencies, not arbitrarily).
>> Also, if you plan to host specifically multimedia files you could
>> consider using XFS instead, I've been told is very good for such
>> purpose ;-)
>
> It is. But keep in mind that XFS is not a filesystem for noobies--not
> plug 'n chug. One need take some time to learn XFS. For instance,
> fsck.xfs doesn't exist. The proper command is "xfs_check" or
> "xfs_repair -n". This is but one example of why "learn then do" is the
> way to go, not the other way around.
Many people have had to learn in the last years how to tweak ext4 to
avoid file system corruption and data loss... I mean, learning how stuff
works is a linux user must, nothing new.
Greetings,
--
Camaleón
Reply to: