public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jose R. Santos" <jrs@us.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: New e2fsprog doc on the ext4 wiki page.
Date: Tue, 24 Jul 2007 11:35:07 -0500	[thread overview]
Message-ID: <20070724113507.72ed9687@rx8> (raw)
In-Reply-To: <46A62672.70808@linux.vnet.ibm.com>

On Tue, 24 Jul 2007 21:48:58 +0530
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:

> 
> 
> Jose R. Santos wrote:
> > Hi folks
> > 
> >
> > 
> > ext4migrate:
> > - Patches submited to the mailing list by Aneesh Kumar
> > http://thread.gmane.org/gmane.comp.file-systems.ext4/1395
> > 
> 
> 
> I guess what we are looking at here is 
> 
> a) ext3 -> ext4 conversion would be done via option for defrag. This
> conversion is now done via a ioctl. This is the suggested method for
> defragmenting an ext3 inode (convert to ext4 and then defrag). 
> 
> b) small inode to large inode conversion is done via tune2fs -I <
> new_inode_size> I have patches for this ready. Will be sending them
> in a day or two.
> 
> So the ext4migrate command may not be really needed.
> 
> 
> -aneesh  

I will remove this item then and add the tune2fs changes.

Is the defrag code going to be part of e2fsprogs or is this going to be
a standalone app?

-JRS

  parent reply	other threads:[~2007-07-24 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 16:07 New e2fsprog doc on the ext4 wiki page Jose R. Santos
2007-07-24 16:18 ` Aneesh Kumar K.V
2007-07-24 16:34   ` Andreas Dilger
2007-07-24 16:35   ` Jose R. Santos [this message]
2007-07-24 17:00     ` Aneesh Kumar K.V
2007-07-25 14:00 ` Amit K. Arora

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=20070724113507.72ed9687@rx8 \
    --to=jrs@us.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox