1config XFS_FS 2 tristate "XFS filesystem support" 3 depends on BLOCK 4 depends on (64BIT || LBDAF) 5 select EXPORTFS 6 select LIBCRC32C 7 select FS_IOMAP 8 help 9 XFS is a high performance journaling filesystem which originated 10 on the SGI IRIX platform. It is completely multi-threaded, can 11 support large files and large filesystems, extended attributes, 12 variable block sizes, is extent based, and makes extensive use of 13 Btrees (directories, extents, free space) to aid both performance 14 and scalability. 15 16 Refer to the documentation at <http://oss.sgi.com/projects/xfs/> 17 for complete details. This implementation is on-disk compatible 18 with the IRIX version of XFS. 19 20 To compile this file system support as a module, choose M here: the 21 module will be called xfs. Be aware, however, that if the file 22 system of your root partition is compiled as a module, you'll need 23 to use an initial ramdisk (initrd) to boot. 24 25config XFS_QUOTA 26 bool "XFS Quota support" 27 depends on XFS_FS 28 select QUOTACTL 29 help 30 If you say Y here, you will be able to set limits for disk usage on 31 a per user and/or a per group basis under XFS. XFS considers quota 32 information as filesystem metadata and uses journaling to provide a 33 higher level guarantee of consistency. The on-disk data format for 34 quota is also compatible with the IRIX version of XFS, allowing a 35 filesystem to be migrated between Linux and IRIX without any need 36 for conversion. 37 38 If unsure, say N. More comprehensive documentation can be found in 39 README.quota in the xfsprogs package. XFS quota can be used either 40 with or without the generic quota support enabled (CONFIG_QUOTA) - 41 they are completely independent subsystems. 42 43config XFS_POSIX_ACL 44 bool "XFS POSIX ACL support" 45 depends on XFS_FS 46 select FS_POSIX_ACL 47 help 48 POSIX Access Control Lists (ACLs) support permissions for users and 49 groups beyond the owner/group/world scheme. 50 51 To learn more about Access Control Lists, visit the POSIX ACLs for 52 Linux website <http://acl.bestbits.at/>. 53 54 If you don't know what Access Control Lists are, say N. 55 56config XFS_RT 57 bool "XFS Realtime subvolume support" 58 depends on XFS_FS 59 help 60 If you say Y here you will be able to mount and use XFS filesystems 61 which contain a realtime subvolume. The realtime subvolume is a 62 separate area of disk space where only file data is stored. It was 63 originally designed to provide deterministic data rates suitable 64 for media streaming applications, but is also useful as a generic 65 mechanism for ensuring data and metadata/log I/Os are completely 66 separated. Regular file I/Os are isolated to a separate device 67 from all other requests, and this can be done quite transparently 68 to applications via the inherit-realtime directory inode flag. 69 70 See the xfs man page in section 5 for additional information. 71 72 If unsure, say N. 73 74config XFS_WARN 75 bool "XFS Verbose Warnings" 76 depends on XFS_FS && !XFS_DEBUG 77 help 78 Say Y here to get an XFS build with many additional warnings. 79 It converts ASSERT checks to WARN, so will log any out-of-bounds 80 conditions that occur that would otherwise be missed. It is much 81 lighter weight than XFS_DEBUG and does not modify algorithms and will 82 not cause the kernel to panic on non-fatal errors. 83 84 However, similar to XFS_DEBUG, it is only advisable to use this if you 85 are debugging a particular problem. 86 87config XFS_DEBUG 88 bool "XFS Debugging support" 89 depends on XFS_FS 90 help 91 Say Y here to get an XFS build with many debugging features, 92 including ASSERT checks, function wrappers around macros, 93 and extra sanity-checking functions in various code paths. 94 95 Note that the resulting code will be HUGE and SLOW, and probably 96 not useful unless you are debugging a particular problem. 97 98 Say N unless you are an XFS developer, or you play one on TV. 99 100config XFS_ASSERT_FATAL 101 bool "XFS fatal asserts" 102 default y 103 depends on XFS_FS && XFS_DEBUG 104 help 105 Set the default DEBUG mode ASSERT failure behavior. 106 107 Say Y here to cause DEBUG mode ASSERT failures to result in fatal 108 errors that BUG() the kernel by default. If you say N, ASSERT failures 109 result in warnings. 110 111 This behavior can be modified at runtime via sysfs. 112