Kconfig 6.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. config XFS_FS
  3. tristate "XFS filesystem support"
  4. depends on BLOCK
  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. Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
  16. for complete details. This implementation is on-disk compatible
  17. with the IRIX version of XFS.
  18. To compile this file system support as a module, choose M here: the
  19. module will be called xfs. Be aware, however, that if the file
  20. system of your root partition is compiled as a module, you'll need
  21. to use an initial ramdisk (initrd) to boot.
  22. config XFS_SUPPORT_V4
  23. bool "Support deprecated V4 (crc=0) format"
  24. depends on XFS_FS
  25. default y
  26. help
  27. The V4 filesystem format lacks certain features that are supported
  28. by the V5 format, such as metadata checksumming, strengthened
  29. metadata verification, and the ability to store timestamps past the
  30. year 2038. Because of this, the V4 format is deprecated. All users
  31. should upgrade by backing up their files, reformatting, and restoring
  32. from the backup.
  33. Administrators and users can detect a V4 filesystem by running
  34. xfs_info against a filesystem mountpoint and checking for a string
  35. beginning with "crc=". If the string "crc=0" is found, the
  36. filesystem is a V4 filesystem. If no such string is found, please
  37. upgrade xfsprogs to the latest version and try again.
  38. This option will become default N in September 2025. Support for the
  39. V4 format will be removed entirely in September 2030. Distributors
  40. can say N here to withdraw support earlier.
  41. To continue supporting the old V4 format (crc=0), say Y.
  42. To close off an attack surface, say N.
  43. config XFS_QUOTA
  44. bool "XFS Quota support"
  45. depends on XFS_FS
  46. select QUOTACTL
  47. help
  48. If you say Y here, you will be able to set limits for disk usage on
  49. a per user and/or a per group basis under XFS. XFS considers quota
  50. information as filesystem metadata and uses journaling to provide a
  51. higher level guarantee of consistency. The on-disk data format for
  52. quota is also compatible with the IRIX version of XFS, allowing a
  53. filesystem to be migrated between Linux and IRIX without any need
  54. for conversion.
  55. If unsure, say N. More comprehensive documentation can be found in
  56. README.quota in the xfsprogs package. XFS quota can be used either
  57. with or without the generic quota support enabled (CONFIG_QUOTA) -
  58. they are completely independent subsystems.
  59. config XFS_POSIX_ACL
  60. bool "XFS POSIX ACL support"
  61. depends on XFS_FS
  62. select FS_POSIX_ACL
  63. help
  64. POSIX Access Control Lists (ACLs) support permissions for users and
  65. groups beyond the owner/group/world scheme.
  66. If you don't know what Access Control Lists are, say N.
  67. config XFS_RT
  68. bool "XFS Realtime subvolume support"
  69. depends on XFS_FS
  70. help
  71. If you say Y here you will be able to mount and use XFS filesystems
  72. which contain a realtime subvolume. The realtime subvolume is a
  73. separate area of disk space where only file data is stored. It was
  74. originally designed to provide deterministic data rates suitable
  75. for media streaming applications, but is also useful as a generic
  76. mechanism for ensuring data and metadata/log I/Os are completely
  77. separated. Regular file I/Os are isolated to a separate device
  78. from all other requests, and this can be done quite transparently
  79. to applications via the inherit-realtime directory inode flag.
  80. See the xfs man page in section 5 for additional information.
  81. If unsure, say N.
  82. config XFS_ONLINE_SCRUB
  83. bool "XFS online metadata check support"
  84. default n
  85. depends on XFS_FS
  86. help
  87. If you say Y here you will be able to check metadata on a
  88. mounted XFS filesystem. This feature is intended to reduce
  89. filesystem downtime by supplementing xfs_repair. The key
  90. advantage here is to look for problems proactively so that
  91. they can be dealt with in a controlled manner.
  92. This feature is considered EXPERIMENTAL. Use with caution!
  93. See the xfs_scrub man page in section 8 for additional information.
  94. If unsure, say N.
  95. config XFS_ONLINE_REPAIR
  96. bool "XFS online metadata repair support"
  97. default n
  98. depends on XFS_FS && XFS_ONLINE_SCRUB
  99. help
  100. If you say Y here you will be able to repair metadata on a
  101. mounted XFS filesystem. This feature is intended to reduce
  102. filesystem downtime by fixing minor problems before they cause the
  103. filesystem to go down. However, it requires that the filesystem be
  104. formatted with secondary metadata, such as reverse mappings and inode
  105. parent pointers.
  106. This feature is considered EXPERIMENTAL. Use with caution!
  107. See the xfs_scrub man page in section 8 for additional information.
  108. If unsure, say N.
  109. config XFS_WARN
  110. bool "XFS Verbose Warnings"
  111. depends on XFS_FS && !XFS_DEBUG
  112. help
  113. Say Y here to get an XFS build with many additional warnings.
  114. It converts ASSERT checks to WARN, so will log any out-of-bounds
  115. conditions that occur that would otherwise be missed. It is much
  116. lighter weight than XFS_DEBUG and does not modify algorithms and will
  117. not cause the kernel to panic on non-fatal errors.
  118. However, similar to XFS_DEBUG, it is only advisable to use this if you
  119. are debugging a particular problem.
  120. config XFS_DEBUG
  121. bool "XFS Debugging support"
  122. depends on XFS_FS
  123. help
  124. Say Y here to get an XFS build with many debugging features,
  125. including ASSERT checks, function wrappers around macros,
  126. and extra sanity-checking functions in various code paths.
  127. Note that the resulting code will be HUGE and SLOW, and probably
  128. not useful unless you are debugging a particular problem.
  129. Say N unless you are an XFS developer, or you play one on TV.
  130. config XFS_ASSERT_FATAL
  131. bool "XFS fatal asserts"
  132. default y
  133. depends on XFS_FS && XFS_DEBUG
  134. help
  135. Set the default DEBUG mode ASSERT failure behavior.
  136. Say Y here to cause DEBUG mode ASSERT failures to result in fatal
  137. errors that BUG() the kernel by default. If you say N, ASSERT failures
  138. result in warnings.
  139. This behavior can be modified at runtime via sysfs.