ext3/ext4 Documentation: remove bh/nobh since it has been deprecated

Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

kernel os linux

Bh and nobh mount option has been deprecated in ext4
(206f7ab4f49a2021fcb8687f25395be77711ddee) and in ext3
(4c4d3901225518ed1a4c938ba15ba09842a00770)
so remove those options from documentation.

Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Jan Kara <jack@suse.cz>

authored by

Lukas Czerner and committed by

Jan Kara 15 years ago ad434017 ee3e77f1

+7 -25

2 changed files

expand all

Documentation

filesystems

ext3.txt

ext4.txt

-9

Documentation/filesystems/ext3.txt

··· 147 147 package for more details 148 148 (http://sourceforge.net/projects/linuxquota). 149 149 150 - bh (*) ext3 associates buffer heads to data pages to 151 - nobh (a) cache disk block mapping information 152 - (b) link pages into transaction to provide 153 - ordering guarantees. 154 - "bh" option forces use of buffer heads. 155 - "nobh" option tries to avoid associating buffer 156 - heads (supported only for "writeback" mode). 157 - 158 - 159 150 Specification 160 151 ============= 161 152 Ext3 shares all disk implementation with the ext2 filesystem, and adds

+7 -16

Documentation/filesystems/ext4.txt

··· 68 68 '-o barriers=[0|1]' mount option for both ext3 and ext4 filesystems 69 69 for a fair comparison. When tuning ext3 for best benchmark numbers, 70 70 it is often worthwhile to try changing the data journaling mode; '-o 71 - data=writeback,nobh' can be faster for some workloads. (Note 72 - however that running mounted with data=writeback can potentially 73 - leave stale data exposed in recently written files in case of an 74 - unclean shutdown, which could be a security exposure in some 75 - situations.) Configuring the filesystem with a large journal can 76 - also be helpful for metadata-intensive workloads. 71 + data=writeback' can be faster for some workloads. (Note however that 72 + running mounted with data=writeback can potentially leave stale data 73 + exposed in recently written files in case of an unclean shutdown, 74 + which could be a security exposure in some situations.) Configuring 75 + the filesystem with a large journal can also be helpful for 76 + metadata-intensive workloads. 77 77 78 78 2. Features 79 79 =========== ··· 272 272 package for more details 273 273 (http://sourceforge.net/projects/linuxquota). 274 274 275 - bh (*) ext4 associates buffer heads to data pages to 276 - nobh (a) cache disk block mapping information 277 - (b) link pages into transaction to provide 278 - ordering guarantees. 279 - "bh" option forces use of buffer heads. 280 - "nobh" option tries to avoid associating buffer 281 - heads (supported only for "writeback" mode). 282 - 283 275 stripe=n Number of filesystem blocks that mballoc will try 284 276 to use for allocation size and alignment. For RAID5/6 285 277 systems this should be the number of data ··· 385 393 write and convert the extent to initialized after IO 386 394 completes. This approach allows ext4 code to avoid 387 395 using inode mutex, which improves scalability on high 388 - speed storages. However this does not work with nobh 389 - option and the mount will fail. Nor does it work with 396 + speed storages. However this does not work with 390 397 data journaling and dioread_nolock option will be 391 398 ignored with kernel warning. Note that dioread_nolock 392 399 code path is only used for extent-based files.