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