From: Xiang Wang <xiangw@google.com>
To: linux-ext4@vger.kernel.org, ext4-team <ext4-team@google.com>
Subject: Options for migrating existing files on ext2 partitions to ext4
Date: Wed, 11 Feb 2009 12:18:09 -0800 [thread overview]
Message-ID: <d5ca277e0902111218l1b568724l2557315d2945637a@mail.gmail.com> (raw)
Hey,
Since we are thinking of switching into using the ext4 file systems on
some of our machines with purely ext2 partitions, we face the problem
of how to migrate all those existing files on ext2 partitions. Seems
like there are two major directions to go:
1) do a backup, umount, mke2fs into ext4, and restore
In this approach, we may actually take advantage of the layout changes
so as to benefit from some features of ext4.
2) umount, tune2fs to add the 'extent' feature, mount back using type
ext4, migrate the existing files(directories) one by one through the
ioctl EXT4_IOC_MIGRATE
Motivated by the ext4 ioctl interface for migration, we are also
looking into this in-place approach. But we are mostly concerned with
the fact that if the existing files are highly fragmented, will we
still get benefit from the extents? Or will we even get hurt by
turning the files into being extents-based?
Before we do more detailed experiments on both approaches, we are here
to ask for advice, suggestion and comments.
So If you have ever run into either direction or even both, do you
have any experience you can share with us? Or simply express your
feeling:
Does it work? What could go wrong?
Does it take very long to complete the migration(of course, it could
depends on the number of files and their data block locations)?
Are you happy with the resulting files being migrated?
Has anyone every tried approach 2)? How did that work for you?
Thanks,
Xiang
next reply other threads:[~2009-02-11 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 20:18 Xiang Wang [this message]
2009-02-12 7:23 ` Options for migrating existing files on ext2 partitions to ext4 Andreas Dilger
2009-02-12 7:57 ` Aneesh Kumar K.V
2009-02-12 8:01 ` Michael Rubin
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=d5ca277e0902111218l1b568724l2557315d2945637a@mail.gmail.com \
--to=xiangw@google.com \
--cc=ext4-team@google.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