From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [RFC][take 4] e2fsprogs: Add ext4migrate
Date: Mon, 07 May 2007 08:56:11 +0530 [thread overview]
Message-ID: <463E9C53.8000503@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070506051759.GP6220@schatzie.adilger.int>
Andreas Dilger wrote:
> On May 04, 2007 14:43 +0530, Aneesh Kumar K.V wrote:
>> Changes from from my previous patches are as follows:
>> a) support for files with holes
>> b) use the block iterator present in libext2fs
>> c) don't mark the indirect blocks as unused early. If we mark the
>> the blocks unused, they can be resued for extent index. If we later
>> fail to migrate, the indirect blocks content would be overwritten.
>
> If this code could also (or optionally just) increase the size of inodes
> it would be very useful. AFAIK right now it will only change the inodes
> from block-mapped to extent-mapped?
>
>
That is correct. My next step is to enhance the tool to support
migration to large inodes.
-aneesh
next prev parent reply other threads:[~2007-05-07 3:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 9:13 [RFC][take 4] e2fsprogs: Add ext4migrate Aneesh Kumar K.V
2007-05-04 9:13 ` [PATCH 1/4] Add unix COW io manager Aneesh Kumar K.V
2007-05-04 9:13 ` Aneesh Kumar K.V
2007-05-04 9:13 ` [PATCH 2/4] Add extent related functions Aneesh Kumar K.V
2007-05-04 9:13 ` Aneesh Kumar K.V
2007-05-04 9:13 ` [PATCH 3/4] e2fsprogs: Add ext4migrate Aneesh Kumar K.V
2007-05-04 9:13 ` Aneesh Kumar K.V
2007-05-04 9:13 ` [PATCH 4/4] Add ext4replay tool Aneesh Kumar K.V
2007-05-04 9:13 ` Aneesh Kumar K.V
2007-05-07 13:01 ` [PATCH 1/4] Add unix COW io manager Theodore Tso
2007-05-06 5:17 ` [RFC][take 4] e2fsprogs: Add ext4migrate Andreas Dilger
2007-05-07 3:26 ` Aneesh Kumar K.V [this message]
2007-05-07 13:20 ` Theodore Tso
2007-05-07 13:46 ` Aneesh Kumar K.V
2007-05-07 15:57 ` Theodore Tso
2007-05-07 21:01 ` Andreas Dilger
2007-05-07 13:59 ` Aneesh Kumar K.V
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=463E9C53.8000503@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@clusterfs.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 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.