public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar" <aneesh.kumar@gmail.com>
To: "Andreas Dilger" <adilger@clusterfs.com>
Cc: "Avantika Mathur" <mathur@linux.vnet.ibm.com>,
	linux-ext4@vger.kernel.org
Subject: Re: Ext4 devel interlock meeting minutes (March 7, 2007)
Date: Sun, 11 Mar 2007 14:25:41 +0530	[thread overview]
Message-ID: <cc723f590703110055m38e1f347scde9b16b8ff9fad7@mail.gmail.com> (raw)
In-Reply-To: <20070308230326.GI5823@schatzie.adilger.int>

On 3/9/07, Andreas Dilger <adilger@clusterfs.com> wrote:
> On Mar 08, 2007  10:06 -0800, Avantika Mathur wrote:
> >
>
> > - Aneesh Veetil has been working on a migration tool from block based to
> > extents allocation. He is looking at two options.
> >
> >    - Offline Migration: Modify e2fsprogs code to actually be able to create
> >    extents. This involves a lot of duplication of ext4 code (btree).
> >    e2fsprogs has code for interpreting extents, but code for creating them
> >    would have to be duplicated.
> >
> >    - Online Migration: Use existing filesystem code to convert to extents -
> >    similar to online defragmentation.
>
> I would prefer to implement this using the same code as the online defrag.
> To be useful, the online defrag has to work with block-mapped files anyways.

Is there a tree (git or hg ) which i can use to get a working online defrag ?

-aneesh

      reply	other threads:[~2007-03-11  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 18:06 Ext4 devel interlock meeting minutes (March 7, 2007) Avantika Mathur
2007-03-08 23:03 ` Andreas Dilger
2007-03-11  8:55   ` Aneesh Kumar [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=cc723f590703110055m38e1f347scde9b16b8ff9fad7@mail.gmail.com \
    --to=aneesh.kumar@gmail.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mathur@linux.vnet.ibm.com \
    /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