public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: tytso@mit.edu
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: [PATCH] 2/11  Ext2/3 Updates: Extended attributes, ACL, etc.
Date: Tue, 29 Oct 2002 12:22:46 -0500	[thread overview]
Message-ID: <3DBEC3E6.9050908@pobox.com> (raw)
In-Reply-To: E186ZRR-0006tS-00@snap.thunk.org

tytso@mit.edu wrote:

>Ext2/3 forward compatibility: on-line resizing
>  
>
Is the interface for this going to be ext2meta?  Al and sct seemed to 
agree that that was the best way act upon the filesystem metadata while 
it's online...  I'll probably be updating that for 2.5.x VFS changes in 
a few weeks, that will provide safe online defrag and a good interface 
for other metadata interaction.

>This patch allows forward compatibility with future filesystems which
>are dynamically grown by using an alternate algorithm for storing the
>block group descriptors.  It's also a bit more efficient, in that it
>uses just a little bit less disk space.  Currently, the ext2 filesystem
>format requires either relocating the inode table, or reserving space in
>before doing the on-line resize.  The new scheme, which is documented in
>"Planned Extensions to the Ext2/3 Filesystem", by Stephen Tweedie and I (see:
>http://www.usenix.org/publications/library/proceedings/usenix02/tech/freenix/tso.html)
>  
>
It would be nice if this paper were available to everybody, and not 
passworded.

    Jeff





  reply	other threads:[~2002-10-29 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 16:42 [PATCH] 2/11 Ext2/3 Updates: Extended attributes, ACL, etc tytso
2002-10-29 17:22 ` Jeff Garzik [this message]
2002-10-31  3:41   ` Theodore Ts'o
2002-11-01  3:22   ` Theodore Ts'o
2002-11-01  3:35     ` Alexander Viro
2002-11-02  8:57     ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31  8:28 tytso

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=3DBEC3E6.9050908@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=tytso@mit.edu \
    /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