From patchwork Sat Jun 12 17:58:30 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Christian Kujau X-Patchwork-Id: 105744 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by demeter.kernel.org (8.14.3/8.14.3) with ESMTP id o5CHwZXA024062 for ; Sat, 12 Jun 2010 17:58:45 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752128Ab0FLR6e (ORCPT ); Sat, 12 Jun 2010 13:58:34 -0400 Received: from moutng.kundenserver.de ([212.227.17.10]:56533 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752107Ab0FLR6c (ORCPT ); Sat, 12 Jun 2010 13:58:32 -0400 Received: from bogon.housecafe.de (ppp-188-174-5-110.dynamic.mnet-online.de [188.174.5.110]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0Mewsn-1OcYzW2gqf-00PHOG; Sat, 12 Jun 2010 19:58:31 +0200 Received: from localhost ([127.0.0.1]) by bogon.housecafe.de with esmtp (Exim 4.69) (envelope-from ) id 1ONUyU-00040Z-Tv; Sat, 12 Jun 2010 19:58:31 +0200 Date: Sat, 12 Jun 2010 10:58:30 -0700 (PDT) From: Christian Kujau To: linux-btrfs@vger.kernel.org cc: LKML Subject: [PATCH] Remove EXPERIMENTAL flag from Btrfs Message-ID: User-Agent: Alpine 2.01 (DEB 1266 2009-07-14) MIME-Version: 1.0 X-Provags-ID: V01U2FsdGVkX19dMX9+/nHN88OpOPQsLMXXJwc8txmxT/FWDhk phgoy8hYxRTWw3Cq/80aTYqIuMUoD4i6sG8kLegrTNnFL546v7 BL0+6CmI5pGFdX5d5p0kg== Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (demeter.kernel.org [140.211.167.41]); Sat, 12 Jun 2010 17:58:45 +0000 (UTC) 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.