linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@enel.ucalgary.ca>
To: LVM on Linux <linux-lvm@msede.com>
Subject: Re: [linux-lvm] Re: ext2resize
Date: Mon, 5 Jul 1999 13:47:41 -0600 (MDT)	[thread overview]
Message-ID: <199907051947.NAA23523@munet-d.enel.ucalgary.ca> (raw)

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

             reply	other threads:[~1999-07-05 19:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-05 19:47 Andreas Dilger [this message]
1999-07-07  5:27 ` [linux-lvm] Re: ext2resize John Finlay
  -- strict thread matches above, loose matches on Subject: below --
1999-07-06  8:56 Lennert Buytenhek
1999-07-06  8:47 Lennert Buytenhek
1999-07-06  7:56 Lennert Buytenhek
1999-07-08 14:34 ` tytso
1999-07-08 22:56 ` Theodore Y. Ts'o
1999-07-05 20:49 Andreas Dilger
1999-07-05  8:47 Lennert Buytenhek
1999-07-05 18:38 ` John Finlay
1999-07-05 18:55 ` John Finlay
1999-07-05  8:40 Lennert Buytenhek
1999-07-04 18:56 Andreas Dilger
1999-06-30  9:46 Admin
1999-07-02 16:58 ` Andreas Dilger
1999-07-05 17:03   ` Stephen C. Tweedie
     [not found] <009c01bebee1$aa81b9a0$0102010a@adminstation.sgymsdam.nl>
1999-06-30  7:34 ` Andreas Dilger

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=199907051947.NAA23523@munet-d.enel.ucalgary.ca \
    --to=adilger@enel.ucalgary.ca \
    --cc=linux-lvm@msede.com \
    /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;
as well as URLs for NNTP newsgroup(s).