All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2/11  Ext2/3 Updates: Extended attributes, ACL, etc.
Date: Thu, 31 Oct 2002 22:22:00 -0500	[thread overview]
Message-ID: <20021101032159.GA12031@think.thunk.org> (raw)
In-Reply-To: <3DBEC3E6.9050908@pobox.com>

On Tue, Oct 29, 2002 at 12:22:46PM -0500, Jeff Garzik wrote:
> 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.

I'm not sure ext2meta will be sufficient.  It's not just a matter of
modifying the on-disk metadata, as would be needed for defrag, but I
would also need to modify some of the in-core data structions in the
ext2/3 filesystem data structures.  For example, when you resize the
filesystem, you need to increase the number of group descriptors,
which means you need to kmalloc, copy, and then kfree sbi->group_desc
out from under the mounted filesystem.

No doubt ext2meta could be modified so it could "reach out and touch"
internal ext2/3 fileststem data structures in core.  But the locking
issues involved get really messy.

My original plan was to adapt Andreas Dilger's on-line resizing patch
to use the new block group layout, which would obviate the need to
take the filesystem off-line and run ext2prepare first.  I'm not
opposed to trying to do it via ext2meta, but it seems like it might
get complicated and hairy quite quickly.

						- Ted

  parent reply	other threads:[~2002-11-01  3:15 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
2002-10-31  3:41   ` Theodore Ts'o
2002-11-01  3:22   ` Theodore Ts'o [this message]
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=20021101032159.GA12031@think.thunk.org \
    --to=tytso@mit.edu \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.