[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] Re: ext2resize

John Finlay <finlay moeraki com> writes:
> It seems that ext2 is not really suited for large filesystems: seems like
> there is too much redundancy in the block groups that causes slow downs in
> operations like mount, etc.; e2fsck takes hours on a 52GB filesystem.

Actually, the new "sparse superblock" version of ext2 available for Linux 2.2
kernels removes much of the redundancy issues for superblocks/group blocks.
Copies are only stored in group 0, and groups which are a power of 3, 5, and
7.  The real issue with large filesystems isn't the redundancy, which is
mostly wasted space and slowdown when unmounting, but rather that the fsck
has to verify the entire FS structure at mount time.  The preferred method
is to have a transaction log/journal which keeps track of outstanding metadata
changes in progress.  When you get a failure, then you only need to replay
the log to see what parts of the FS were being modified at the time, and
then only those areas need to be verified at fsck time.

> Are there any projects underway to develop a new filesystem that is more
> suitable for large filesystems?

There are several log FS/JFS projects underway right now for Linux.
Even SGI will release the source (or so I've read) to their IRIX
filesystem, which is journalled, so this may be added to the mix soon.

Cheers, Andreas
Andreas Dilger   University of Calgary  \"If a man ate a pound of pasta and
                 Micronet Research Group \ a pound of antipasto, would they
Dept of Electrical & Computer Engineering \   cancel out, leaving him still
http://www-mddsp.enel.ucalgary.ca/People/adilger/       hungry?" -- Dogbert

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]