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