From: Yan Zheng <yanzheng@21cn.com>
To: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: New experimental btrfs branch ready for testing
Date: Mon, 8 Jun 2009 20:33:28 +0800 [thread overview]
Message-ID: <3d0408630906080533n3c9c6f75sd80f47b568b99e2c@mail.gmail.com> (raw)
In-Reply-To: <20090601210447.GC3890@think>
2009/6/2 Chris Mason <chris.mason@oracle.com>
>
> Hello everyone,
>
> Yan Zheng has been doing some major surgery to the back references an=
d
> extent allocation code, tackling bottlenecks in the code that tracks
> extents. =A0It scales better with many snapshots and performs better =
in
> the common case of no snapshots at all.
>
> THE NEW CODE IS A FORWARD ROLLING DISK FORMAT CHANGE. =A0This means i=
t is
> compatible with the current btrfs disk format, but once you mount a
> filesystem with the new code, it WILL NO LONGER BE MOUNTABLE FROM OLD
> KERNELS. =A0Old kernels spit out an error message when you try them o=
n new
> format filesystems.
>
Hello, everyone
I have a minor disk format change for the new format. The disk format c=
hange
makes snapshot dropping more efficient. The format change only affects =
=46S
has been balanced. If you are testing the new format, please don't use
btrfs-vol -b or btrfs-vol -r. If you have already used btrfs-vol -b or
btrfs-vol -r,
please backup your data.
Regards
Yan Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-06-08 12:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 21:04 New experimental btrfs branch ready for testing Chris Mason
2009-06-02 13:28 ` Chris Mason
2009-06-03 17:08 ` Chris Mason
2009-06-04 19:02 ` Steven Pratt
2009-06-04 19:05 ` Chris Mason
2009-06-05 14:20 ` Chris Mason
2009-06-05 16:02 ` Steven Pratt
2009-06-05 21:27 ` Steven Pratt
2009-06-06 0:20 ` Chris Mason
2009-06-06 16:38 ` Steven Pratt
2009-06-09 15:26 ` Chris Mason
2009-06-15 15:46 ` Steven Pratt
2009-06-07 11:50 ` Roy Sigurd Karlsbakk
2009-06-07 12:13 ` Daniel Cordero
2009-06-08 12:33 ` Yan Zheng [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=3d0408630906080533n3c9c6f75sd80f47b568b99e2c@mail.gmail.com \
--to=yanzheng@21cn.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@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