From: Christian Kujau <lists@nerdbynature.de>
To: linux-btrfs@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] Remove EXPERIMENTAL flag from Btrfs
Date: Sat, 12 Jun 2010 10:58:30 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.01.1006121027480.3964@bogon.housecafe.de> (raw)
Resubmitting, as it doesn't seem to be upstream yet.
-----------------
Remove EXPERIMENTAL flag from btrfs and also state that the disk format
has indeed been finalized.
Signed-off-by: Christian Kujau <lists@nerdbynature.de>
diff --git a/Documentation/filesystems/btrfs.txt b/Documentation/filesystems/btrfs.txt
index 64087c3..da67070 100644
--- a/Documentation/filesystems/btrfs.txt
+++ b/Documentation/filesystems/btrfs.txt
@@ -12,9 +12,9 @@ number of challenges with scaling to the large storage subsystems that
are becoming common in today's data centers. Filesystems need to scale
in their ability to address and manage large storage, and also in
their ability to detect, repair and tolerate errors in the data stored
-on disk. Btrfs is under heavy development, and is not suitable for
-any uses other than benchmarking and review. The Btrfs disk format is
-not yet finalized.
+on disk. Btrfs is under heavy development, but with Linux 2.6.31 the
+Btrfs disk format has been finalized and is not considered experimental
+any more.
The main Btrfs features include:
@@ -33,6 +33,7 @@ The main Btrfs features include:
* Efficient incremental backup and FS mirroring (not yet implemented)
* Online filesystem defragmentation
+Please see https://btrfs.wiki.kernel.org for details on these features.
MAILING LIST
diff --git a/fs/btrfs/Kconfig b/fs/btrfs/Kconfig
index 7bb3c02..cebb197 100644
--- a/fs/btrfs/Kconfig
+++ b/fs/btrfs/Kconfig
@@ -1,16 +1,12 @@
config BTRFS_FS
- tristate "Btrfs filesystem (EXPERIMENTAL) Unstable disk format"
- depends on EXPERIMENTAL
+ tristate "Btrfs filesystem"
select LIBCRC32C
select ZLIB_INFLATE
select ZLIB_DEFLATE
help
Btrfs is a new filesystem with extents, writable snapshotting,
- support for multiple devices and many more features.
-
- Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET
- FINALIZED. You should say N here unless you are interested in
- testing Btrfs with non-critical data.
+ support for multiple devices and many more features. For more
+ information, please see https://btrfs.wiki.kernel.org.
To compile this file system support as a module, choose M here. The
module will be called btrfs.
--
BOFH excuse #186:
permission denied
reply other threads:[~2010-06-12 17:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.DEB.2.01.1006121027480.3964@bogon.housecafe.de \
--to=lists@nerdbynature.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).