From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-ext4@vger.kernel.org
Subject: Re: [RFC][take 4] e2fsprogs: Add ext4migrate
Date: Mon, 07 May 2007 19:29:04 +0530 [thread overview]
Message-ID: <463F30A8.5010601@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070507132001.GB17180@thunk.org>
Theodore Tso wrote:
>
>> That is correct. My next step is to enhance the tool to support
>> migration to large inodes.
>
> I would actually suggest that the place to add that functionality
> would be via "tune2fs -I <inode_size>". Since mke2fs -I <inode_size>
> is used to set the inode size, it makes sense that tune2fs -I would
> change the inode size. Obviously this would have to be done when the
> filesystem is not mounted, and tune2fs should abort gracefully if
> determines that the filesystem is mounted.
That is nice !!. I will add the large inode migration support to tune2fs.
-aneesh
prev parent reply other threads:[~2007-05-07 13:59 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
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 [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=463F30A8.5010601@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@clusterfs.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 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.