fs/btrfs/Kconfig

   1 config BTRFS_FS
   2         tristate "Btrfs filesystem Unstable disk format"
   3         select LIBCRC32C
   4         select ZLIB_INFLATE
   5         select ZLIB_DEFLATE
   6         select LZO_COMPRESS
   7         select LZO_DECOMPRESS
   8         help
   9           Btrfs is a new filesystem with extents, writable snapshotting,
  10           support for multiple devices and many more features.
  11
  12           Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET
  13           FINALIZED.  You should say N here unless you are interested in
  14           testing Btrfs with non-critical data.
  15
  16           To compile this file system support as a module, choose M here. The
  17           module will be called btrfs.
  18
  19           If unsure, say N.
  20
  21 config BTRFS_FS_POSIX_ACL
  22         bool "Btrfs POSIX Access Control Lists"
  23         depends on BTRFS_FS
  24         select FS_POSIX_ACL
  25         help
  26           POSIX Access Control Lists (ACLs) support permissions for users and
  27           groups beyond the owner/group/world scheme.
  28
  29           To learn more about Access Control Lists, visit the POSIX ACLs for
  30           Linux website <http://acl.bestbits.at/>.
  31
  32           If you don't know what Access Control Lists are, say N
  33
  34 config BTRFS_FS_CHECK_INTEGRITY
  35         bool "Btrfs with integrity check tool compiled in (DANGEROUS)"
  36         depends on BTRFS_FS
  37         help
  38           Adds code that examines all block write requests (including
  39           writes of the super block). The goal is to verify that the
  40           state of the filesystem on disk is always consistent, i.e.,
  41           after a power-loss or kernel panic event the filesystem is
  42           in a consistent state.
  43
  44           If the integrity check tool is included and activated in
  45           the mount options, plenty of kernel memory is used, and
  46           plenty of additional CPU cycles are spent. Enabling this
  47           functionality is not intended for normal use.
  48
  49           In most cases, unless you are a btrfs developer who needs
  50           to verify the integrity of (super)-block write requests
  51           during the run of a regression test, say N