From: Andreas Dilger <adilger@sun.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] Add e4migrate
Date: Fri, 05 Sep 2008 17:44:26 -0600 [thread overview]
Message-ID: <20080905234426.GC3086@webber.adilger.int> (raw)
In-Reply-To: <1220609506-2052-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
On Sep 05, 2008 15:41 +0530, Aneesh Kumar wrote:
> +e4migrate \- Migrate an ext3 inode to ext4 inode format
> +.B e4migrate will migrate filename in ext3 inode format to ext4 inode format
> +This can be used to migrate an ext3 file system to ext4 file system
Can you please explain a bit more about what is done here? Is it changing
block mapped inodes to extent mapped? Resising the inodes/GDT? Changing
other things like growing large inode space for ns timestamps/version?
We have an option to e2fsck (like -D for rehash directory, but instead
"-E expand_extra_isize") to resize the "extra_isize" of an existing inode
to ensure that enough space is in the filesystem for i_version_hi, if it
isn't already. This is in our patch "e2fsprogs-expand-extra-isize.patch"
in the Lustre patchset.
I think it makes more sense to have options for existing tools, rather
than having 10 new different tools, but maybe Ted has other opinions.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
prev parent reply other threads:[~2008-09-05 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 10:11 [PATCH] Add e4migrate Aneesh Kumar K.V
2008-09-05 23:44 ` Andreas Dilger [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=20080905234426.GC3086@webber.adilger.int \
--to=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--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