From: Chris Mason <chris.mason@oracle.com>
To: Yan Zheng <yanzheng@21cn.com>
Cc: linux-btrfs@vger.kernel.org, btrfs-devel@oss.oracle.com
Subject: Re: [Btrfs-devel][PATCH] Updates for ext3 converter.
Date: Tue, 22 Apr 2008 14:30:16 -0400 [thread overview]
Message-ID: <200804221430.17152.chris.mason@oracle.com> (raw)
In-Reply-To: <480D87EA.8080800@21cn.com>
On Tuesday 22 April 2008, Yan Zheng wrote:
> Hello,
>
> This patch updates the ext3 converter. The main changes in this patch
> are adding chunk handing and data relocation ability. In the last step
> of conversion, the converter relocates data in system chunk and move
> chunk tree into system chunk. In the rollback process, the converter
> remove chunk tree from system chunk and copy data back.
Great, I've pushed this out to the unstable trees, along with a btrfs-show
command to give a summary of all the btrfs filesystems on the box.
-chris
prev parent reply other threads:[~2008-04-22 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 6:38 [Btrfs-devel][PATCH] Updates for ext3 converter Yan Zheng
2008-04-22 18:30 ` Chris Mason [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=200804221430.17152.chris.mason@oracle.com \
--to=chris.mason@oracle.com \
--cc=btrfs-devel@oss.oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=yanzheng@21cn.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;
as well as URLs for NNTP newsgroup(s).