| Alexey Dobriyan | 6da0b38 | 2008-10-20 22:28:45 +0400 | [diff] [blame] | 1 | config JBD2 |
| 2 | tristate |
| 3 | select CRC32 |
| 4 | help |
| 5 | This is a generic journaling layer for block devices that support |
| 6 | both 32-bit and 64-bit block numbers. It is currently used by |
| 7 | the ext4 and OCFS2 filesystems, but it could also be used to add |
| 8 | journal support to other file systems or block devices such |
| 9 | as RAID or LVM. |
| 10 | |
| 11 | If you are using ext4 or OCFS2, you need to say Y here. |
| 12 | If you are not using ext4 or OCFS2 then you will |
| 13 | probably want to say N. |
| 14 | |
| 15 | To compile this device as a module, choose M here. The module will be |
| 16 | called jbd2. If you are compiling ext4 or OCFS2 into the kernel, |
| 17 | you cannot compile this code as a module. |
| 18 | |
| 19 | config JBD2_DEBUG |
| 20 | bool "JBD2 (ext4) debugging support" |
| 21 | depends on JBD2 && DEBUG_FS |
| 22 | help |
| 23 | If you are using the ext4 journaled file system (or |
| 24 | potentially any other filesystem/device using JBD2), this option |
| 25 | allows you to enable debugging output while the system is running, |
| 26 | in order to help track down any problems you are having. |
| 27 | By default, the debugging output will be turned off. |
| 28 | |
| 29 | If you select Y here, then you will be able to turn on debugging |
| 30 | with "echo N > /sys/kernel/debug/jbd2/jbd2-debug", where N is a |
| 31 | number between 1 and 5. The higher the number, the more debugging |
| 32 | output is generated. To turn debugging off again, do |
| 33 | "echo 0 > /sys/kernel/debug/jbd2/jbd2-debug". |