linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Theodore Tso <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: [RFC][take 4] e2fsprogs: Add ext4migrate
Date: Mon, 7 May 2007 14:01:15 -0700	[thread overview]
Message-ID: <20070507210115.GB8181@schatzie.adilger.int> (raw)
In-Reply-To: <463F2DB7.6090507@linux.vnet.ibm.com>

On May 07, 2007  19:16 +0530, Aneesh Kumar K.V wrote:
> Theodore Tso wrote:
> >Actually, changing the inode size is actually going to be more useful
> >to a larger number of people, since they can use it today to support
> >in-inode EA's.  In addition, changing the inode size must be done
> >off-line, whereas it's not so clear that off-line conversion to
> >extents is the best way to go (more on that below).
> 
> That way we don't need to add kernel code that convert ext3 inode to 
> ext4 inode while defragmentation. Last time i looked at the online 
> defrag code, i was not able to figure out a easy way to take indirect 
> map inode as input, then defrag the same and write the result in extent 
> map.

I think the online defrag code _should_ be fairly easily made to handle
defrag of block-mapped files, so long as it is always creating extent-
mapped files in the end.  All that should be necessary is to have the
kernel read data from the block-mapped file and write it into the newly
mapped blocks.  That functionality needs to exist for a long time anyways
to support upgrading the filesystem so it shouldn't be a huge burden.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

  parent reply	other threads:[~2007-05-07 21:01 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
     [not found] ` <eb16ba5f2c6f399ea747169097434ae84443728f.1178262585.git.aneesh.kumar@linux.vnet.ibm.com>
2007-05-04  9:13   ` [PATCH 1/4] Add unix COW io manager Aneesh Kumar K.V
     [not found]   ` <344eabfd05e36374043e8cd0b4e166a66f88bec6.1178262586.git.aneesh.kumar@linux.vnet.ibm.com>
2007-05-04  9:13     ` [PATCH 2/4] Add extent related functions Aneesh Kumar K.V
     [not found]   ` <1dcc9dea2106570ec314b59bf69e7e3720818a94.1178262586.git.aneesh.kumar@linux.vnet.ibm.com>
2007-05-04  9:13     ` [PATCH 3/4] e2fsprogs: Add ext4migrate Aneesh Kumar K.V
     [not found]   ` <69f2894044fa7c5ad14a59c22e603bc5529dce2a.1178262586.git.aneesh.kumar@linux.vnet.ibm.com>
2007-05-04  9:13     ` [PATCH 4/4] Add ext4replay tool 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 [this message]
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=20070507210115.GB8181@schatzie.adilger.int \
    --to=adilger@clusterfs.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;
as well as URLs for NNTP newsgroup(s).