Kconfig 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990
  1. config EXT3_FS
  2. tristate "Ext3 journalling file system support"
  3. select JBD
  4. help
  5. This is the journalling version of the Second extended file system
  6. (often called ext3), the de facto standard Linux file system
  7. (method to organize files on a storage device) for hard disks.
  8. The journalling code included in this driver means you do not have
  9. to run e2fsck (file system checker) on your file systems after a
  10. crash. The journal keeps track of any changes that were being made
  11. at the time the system crashed, and can ensure that your file system
  12. is consistent without the need for a lengthy check.
  13. Other than adding the journal to the file system, the on-disk format
  14. of ext3 is identical to ext2. It is possible to freely switch
  15. between using the ext3 driver and the ext2 driver, as long as the
  16. file system has been cleanly unmounted, or e2fsck is run on the file
  17. system.
  18. To add a journal on an existing ext2 file system or change the
  19. behavior of ext3 file systems, you can use the tune2fs utility ("man
  20. tune2fs"). To modify attributes of files and directories on ext3
  21. file systems, use chattr ("man chattr"). You need to be using
  22. e2fsprogs version 1.20 or later in order to create ext3 journals
  23. (available at <http://sourceforge.net/projects/e2fsprogs/>).
  24. To compile this file system support as a module, choose M here: the
  25. module will be called ext3.
  26. config EXT3_DEFAULTS_TO_ORDERED
  27. bool "Default to 'data=ordered' in ext3"
  28. depends on EXT3_FS
  29. default y
  30. help
  31. The journal mode options for ext3 have different tradeoffs
  32. between when data is guaranteed to be on disk and
  33. performance. The use of "data=writeback" can cause
  34. unwritten data to appear in files after an system crash or
  35. power failure, which can be a security issue. However,
  36. "data=ordered" mode can also result in major performance
  37. problems, including seconds-long delays before an fsync()
  38. call returns. For details, see:
  39. http://ext4.wiki.kernel.org/index.php/Ext3_data_mode_tradeoffs
  40. If you have been historically happy with ext3's performance,
  41. data=ordered mode will be a safe choice and you should
  42. answer 'y' here. If you understand the reliability and data
  43. privacy issues of data=writeback and are willing to make
  44. that trade off, answer 'n'.
  45. config EXT3_FS_XATTR
  46. bool "Ext3 extended attributes"
  47. depends on EXT3_FS
  48. default y
  49. help
  50. Extended attributes are name:value pairs associated with inodes by
  51. the kernel or by users (see the attr(5) manual page, or visit
  52. <http://acl.bestbits.at/> for details).
  53. If unsure, say N.
  54. You need this for POSIX ACL support on ext3.
  55. config EXT3_FS_POSIX_ACL
  56. bool "Ext3 POSIX Access Control Lists"
  57. depends on EXT3_FS_XATTR
  58. select FS_POSIX_ACL
  59. help
  60. Posix Access Control Lists (ACLs) support permissions for users and
  61. groups beyond the owner/group/world scheme.
  62. To learn more about Access Control Lists, visit the Posix ACLs for
  63. Linux website <http://acl.bestbits.at/>.
  64. If you don't know what Access Control Lists are, say N
  65. config EXT3_FS_SECURITY
  66. bool "Ext3 Security Labels"
  67. depends on EXT3_FS_XATTR
  68. help
  69. Security labels support alternative access control models
  70. implemented by security modules like SELinux. This option
  71. enables an extended attribute handler for file security
  72. labels in the ext3 filesystem.
  73. If you are not using a security module that requires using
  74. extended attributes for file security labels, say N.