linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Frank Mayhar <fmayhar@google.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Concise description of disk layout?
Date: Fri, 17 Apr 2009 15:36:44 -0400	[thread overview]
Message-ID: <20090417193644.GD26479@mit.edu> (raw)
In-Reply-To: <1239994166.7799.24.camel@bobble.smo.corp.google.com>

On Fri, Apr 17, 2009 at 11:49:26AM -0700, Frank Mayhar wrote:
> On Fri, 2009-04-17 at 18:30 +0000, Frank Mayhar wrote:
> > Sorry for the late reply.
> > 
> > On Wed, 15 Apr 2009 20:28:09 -0400, Theodore Tso wrote:
> > >    http://e2fsprogs.sourceforge.net/ext2intro.html
> > > 
> > > but updated for ext4?
> > 
> > Yeah, the "Physical Structure" section.
> 
> I've read through some of the documents you pointed to and it sounds
> like the actual on-disk format hasn't changed significantly, i.e. block
> groups are laid out in basically the same way and the stuff within them
> is laid out in more or less the same way as in ext2/ext3; the major
> difference seems to be the allocation strategies embedded in the code
> itself.  The new strategies simply mean that files and inodes are
> allocated more efficiently but not really in new places.  Is this (more
> or less) correct or am I totally off-base?

The biggest structural change would be the extent allocation trees,
and the flex_bg changes, which move the block and inode bitmaps and
the inode table out of their individual block groups, and group them
together into larger units.  Take a a look at the dumpe2fs output of a
freshly created ext4 filesystem, and that should become clear.  

On the whole, though, you're correct; the overall on-disk structure
really hasn't changed that much.  Inodes have gotten bigger, and for
64-bit block-sized filesystems, the block group descriptors will also
get bigger, and of course the ext2 description doesn't talk about
where extended attributes are stored, or the htree directory
structures.  But the changes in ext2/3/4 have always been
evolutionary.

Regards,

					- Ted

      reply	other threads:[~2009-04-17 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 23:33 Concise description of disk layout? Frank Mayhar
2009-04-16  0:28 ` Theodore Tso
2009-04-16  0:49   ` Eric Sandeen
2009-04-17 18:30   ` Frank Mayhar
2009-04-17 18:49     ` Frank Mayhar
2009-04-17 19:36       ` Theodore Tso [this message]

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=20090417193644.GD26479@mit.edu \
    --to=tytso@mit.edu \
    --cc=fmayhar@google.com \
    --cc=linux-ext4@vger.kernel.org \
    /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).