From: Michael Rubin <mrubin@google.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Andreas Dilger <adilger@sun.com>, Xiang Wang <xiangw@google.com>,
linux-ext4@vger.kernel.org, ext4-team <ext4-team@google.com>
Subject: Re: Options for migrating existing files on ext2 partitions to ext4
Date: Thu, 12 Feb 2009 00:01:21 -0800 [thread overview]
Message-ID: <532480950902120001l213162a8k26d4499d25b4cede@mail.gmail.com> (raw)
In-Reply-To: <20090212075734.GA21074@skywalker>
On Wed, Feb 11, 2009 at 11:57 PM, Aneesh Kumar K.V
<aneesh.kumar@linux.vnet.ibm.com> wrote:
> The plan was to hook the migrate interface with defrag so that after
> migrate we run a defrag on that that would move data blocks around.
Any data showing amount of time it takes to perform either the migrate
only or defrag-then-migrate operations on a disk both offline and
online?
mrubin
prev parent reply other threads:[~2009-02-12 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 20:18 Options for migrating existing files on ext2 partitions to ext4 Xiang Wang
2009-02-12 7:23 ` Andreas Dilger
2009-02-12 7:57 ` Aneesh Kumar K.V
2009-02-12 8:01 ` Michael Rubin [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=532480950902120001l213162a8k26d4499d25b4cede@mail.gmail.com \
--to=mrubin@google.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=ext4-team@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=xiangw@google.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