Kconfig 3.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293
  1. config BTRFS_FS
  2. tristate "Btrfs filesystem support"
  3. select CRYPTO
  4. select CRYPTO_CRC32C
  5. select ZLIB_INFLATE
  6. select ZLIB_DEFLATE
  7. select LZO_COMPRESS
  8. select LZO_DECOMPRESS
  9. select ZSTD_COMPRESS
  10. select ZSTD_DECOMPRESS
  11. select RAID6_PQ
  12. select XOR_BLOCKS
  13. select SRCU
  14. help
  15. Btrfs is a general purpose copy-on-write filesystem with extents,
  16. writable snapshotting, support for multiple devices and many more
  17. features focused on fault tolerance, repair and easy administration.
  18. The filesystem disk format is no longer unstable, and it's not
  19. expected to change unless there are strong reasons to do so. If there
  20. is a format change, file systems with a unchanged format will
  21. continue to be mountable and usable by newer kernels.
  22. For more information, please see the web pages at
  23. http://btrfs.wiki.kernel.org.
  24. To compile this file system support as a module, choose M here. The
  25. module will be called btrfs.
  26. If unsure, say N.
  27. config BTRFS_FS_POSIX_ACL
  28. bool "Btrfs POSIX Access Control Lists"
  29. depends on BTRFS_FS
  30. select FS_POSIX_ACL
  31. help
  32. POSIX Access Control Lists (ACLs) support permissions for users and
  33. groups beyond the owner/group/world scheme.
  34. To learn more about Access Control Lists, visit the POSIX ACLs for
  35. Linux website <http://acl.bestbits.at/>.
  36. If you don't know what Access Control Lists are, say N
  37. config BTRFS_FS_CHECK_INTEGRITY
  38. bool "Btrfs with integrity check tool compiled in (DANGEROUS)"
  39. depends on BTRFS_FS
  40. help
  41. Adds code that examines all block write requests (including
  42. writes of the super block). The goal is to verify that the
  43. state of the filesystem on disk is always consistent, i.e.,
  44. after a power-loss or kernel panic event the filesystem is
  45. in a consistent state.
  46. If the integrity check tool is included and activated in
  47. the mount options, plenty of kernel memory is used, and
  48. plenty of additional CPU cycles are spent. Enabling this
  49. functionality is not intended for normal use.
  50. In most cases, unless you are a btrfs developer who needs
  51. to verify the integrity of (super)-block write requests
  52. during the run of a regression test, say N
  53. config BTRFS_FS_RUN_SANITY_TESTS
  54. bool "Btrfs will run sanity tests upon loading"
  55. depends on BTRFS_FS
  56. help
  57. This will run some basic sanity tests on the free space cache
  58. code to make sure it is acting as it should. These are mostly
  59. regression tests and are only really interesting to btrfs
  60. developers.
  61. If unsure, say N.
  62. config BTRFS_DEBUG
  63. bool "Btrfs debugging support"
  64. depends on BTRFS_FS
  65. help
  66. Enable run-time debugging support for the btrfs filesystem. This may
  67. enable additional and expensive checks with negative impact on
  68. performance, or export extra information via sysfs.
  69. If unsure, say N.
  70. config BTRFS_ASSERT
  71. bool "Btrfs assert support"
  72. depends on BTRFS_FS
  73. help
  74. Enable run-time assertion checking. This will result in panics if
  75. any of the assertions trip. This is meant for btrfs developers only.
  76. If unsure, say N.