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