Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs
Pull btrfs fixes from Chris Mason: "Almost all of these are bug fixes. Dave Sterba's documentation update is the big exception because he removed our promises to set any machine running Btrfs on fire" * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs: Documentation: filesystems: update btrfs tools section Documentation: filesystems: add new btrfs mount options btrfs: update kconfig help text btrfs: fix bio_size_ok() for max_sectors > 0xffff btrfs: Use trace condition for get_extent tracepoint btrfs: fix typo in the log message Btrfs: fix list delete warning when removing ordered root from the list Btrfs: print bytenr instead of page pointer in check-int Btrfs: remove dead codes from ctree.h Btrfs: don't wait for ordered data outside desired range Btrfs: fix lockdep error in async commit Btrfs: avoid heavy operations in btrfs_commit_super Btrfs: fix __btrfs_start_workers retval Btrfs: disable online raid-repair on ro mounts Btrfs: do not inc uncorrectable_errors counter on ro scrubs Btrfs: only drop modified extents if we logged the whole inode Btrfs: make sure to copy everything if we rename Btrfs: don't BUG_ON() if we get an error walking backrefs
This commit is contained in:
@@ -9,12 +9,17 @@ config BTRFS_FS
|
||||
select XOR_BLOCKS
|
||||
|
||||
help
|
||||
Btrfs is a new filesystem with extents, writable snapshotting,
|
||||
support for multiple devices and many more features.
|
||||
Btrfs is a general purpose copy-on-write filesystem with extents,
|
||||
writable snapshotting, support for multiple devices and many more
|
||||
features focused on fault tolerance, repair and easy administration.
|
||||
|
||||
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.
|
||||
The filesystem disk format is no longer unstable, and it's not
|
||||
expected to change unless there are strong reasons to do so. If there
|
||||
is a format change, file systems with a unchanged format will
|
||||
continue to be mountable and usable by newer kernels.
|
||||
|
||||
For more information, please see the web pages at
|
||||
http://btrfs.wiki.kernel.org.
|
||||
|
||||
To compile this file system support as a module, choose M here. The
|
||||
module will be called btrfs.
|
||||
|
Reference in New Issue
Block a user