>16tb filesystems on linux
poweredge at antibozo.net
Thu Aug 26 19:55:01 CDT 2010
On 2010-08-26 17:26, Nick Stephens wrote:
> Does anyone have any tips or tricks for this scenario? I am utilizing
> RHEL5 based installations, btw.
Don't create very large filesystems.
- Very large filesystems take a long time to fsck. Using smaller
filesystems with LVM snapshots lets you fsck periodically without even
umounting your filesystems.
- A serious error or inconsistency in a very large filesystem may blow
away all of your data; smaller filesystems constrain the damage.
- The properties of one giant filesystem (e.g. striping, inode/block
ratio) can't be tuned to the different needs of different types of files
you might store. Your application might be more efficient if it put
larger files on a different filesystem with a better large-file
- Very large filesystems limit you to a small subset of possible
- Very large filesystems keep you from migrating your data to
off-the-shelf hardware in an emergency.
- You're going to hit limits of some kind sooner or later, so your
application should be designed to tolerate having your data on multiple
More information about the Linux-PowerEdge