Kconfig 2.9 KB

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