# SPDX-License-Identifier: GPL-2.0
config [31mCONFIG_BTRFS_FS[0m
tristate "Btrfs filesystem support"
select [31mCONFIG_CRYPTO[0m
select [31mCONFIG_CRYPTO_CRC32C[0m
select [31mCONFIG_LIBCRC32C[0m
select [31mCONFIG_ZLIB_INFLATE[0m
select [31mCONFIG_ZLIB_DEFLATE[0m
select [31mCONFIG_LZO_COMPRESS[0m
select [31mCONFIG_LZO_DECOMPRESS[0m
select [31mCONFIG_ZSTD_COMPRESS[0m
select [31mCONFIG_ZSTD_DECOMPRESS[0m
select [31mCONFIG_RAID6_PQ[0m
select [31mCONFIG_XOR_BLOCKS[0m
select [31mCONFIG_SRCU[0m
help
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.
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 [31mCONFIG_M[0m here. The
module will be called btrfs.
If unsure, say N.
config [31mCONFIG_BTRFS_FS_POSIX_ACL[0m
bool "Btrfs POSIX Access Control Lists"
depends on [31mCONFIG_BTRFS_FS[0m
select [31mCONFIG_FS_POSIX_ACL[0m
help
POSIX Access Control Lists (ACLs) support permissions for users and
groups beyond the owner/group/world scheme.
If you don't know what Access Control Lists are, say N
config [31mCONFIG_BTRFS_FS_CHECK_INTEGRITY[0m
bool "Btrfs with integrity check tool compiled in (DANGEROUS)"
depends on [31mCONFIG_BTRFS_FS[0m
help
Adds code that examines all block write requests (including
writes of the super block). The goal is to verify that the
state of the filesystem on disk is always consistent, i.e.,
after a power-loss or kernel panic event the filesystem is
in a consistent state.
If the integrity check tool is included and activated in
the mount options, plenty of kernel memory is used, and
plenty of additional CPU cycles are spent. Enabling this
functionality is not intended for normal use.
In most cases, unless you are a btrfs developer who needs
to verify the integrity of (super)-block write requests
during the run of a regression test, say N
config [31mCONFIG_BTRFS_FS_RUN_SANITY_TESTS[0m
bool "Btrfs will run sanity tests upon loading"
depends on [31mCONFIG_BTRFS_FS[0m
help
This will run some basic sanity tests on the free space cache
code to make sure it is acting as it should. These are mostly
regression tests and are only really interesting to btrfs
developers.
If unsure, say N.
config [31mCONFIG_BTRFS_DEBUG[0m
bool "Btrfs debugging support"
depends on [31mCONFIG_BTRFS_FS[0m
help
Enable run-time debugging support for the btrfs filesystem. This may
enable additional and expensive checks with negative impact on
performance, or export extra information via sysfs.
If unsure, say N.
config [31mCONFIG_BTRFS_ASSERT[0m
bool "Btrfs assert support"
depends on [31mCONFIG_BTRFS_FS[0m
help
Enable run-time assertion checking. This will result in panics if
any of the assertions trip. This is meant for btrfs developers only.
If unsure, say N.
config [31mCONFIG_BTRFS_FS_REF_VERIFY[0m
bool "Btrfs with the ref verify tool compiled in"
depends on [31mCONFIG_BTRFS_FS[0m
default n
help
Enable run-time extent reference verification instrumentation. This
is meant to be used by btrfs developers for tracking down extent
reference problems or verifying they didn't break something.
If unsure, say N.