Kconfig 2.9 KB

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