RepoMirrors
/
btrfs-progs
mirror of https://github.com/kdave/btrfs-progs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

btrfs-progs: small fixes/cleanup in Documentation 

The removed paragraph in btrfs-man5.asciidoc says the same as the
previous one.

Signed-off-by: Merlin Büge <merlin.buege@tuhh.de>
Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
Merlin Büge 2019-10-18 18:14:33 +02:00 committed by David Sterba
parent 34ef695a81
commit 99d6346048
2 changed files with 6 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/btrfs-man5.asciidoc
View File

@ -231,12 +231,6 @@ during a period of low system activity will prevent latent interference with
the performance of other operations. Also, a device may ignore the TRIM command
if the range is too small, so running a batch discard has a greater probability
of actually discarding the blocks.
+
If discarding is not necessary to be done at the block freeing time, there's
`fstrim`(8) tool that lets the filesystem discard all free blocks in a batch,
possibly not much interfering with other operations. Also, the device may
ignore the TRIM command if the range is too small, so running the batch discard
can actually discard the blocks.
*enospc_debug*::
*noenospc_debug*::
@ -666,7 +660,7 @@ swapfile extents or may fail:
* resize shrink - works as long as the extents are outside of the shrunk range
* device add - a new device does not interfere with existing swapfile and this operation will work, though no new swapfile can be activated afterwards
* device delete - if the device has been added as above, it can be also deleted
* device replace - dtto
* device replace - ditto
When there are no active swapfiles and a whole-filesystem exclusive operation
is running (ie. balance, device delete, shrink), the swapfiles cannot be

10
Documentation/mkfs.btrfs.asciidoc
View File

@ -27,17 +27,17 @@ mkfs.btrfs uses the entire device space for the filesystem.
*-d|--data <profile>*::
Specify the profile for the data block groups. Valid values are 'raid0',
'raid1', 'raid5', 'raid6', 'raid10' or 'single' or dup (case does not matter).
'raid1', 'raid5', 'raid6', 'raid10' or 'single' or 'dup' (case does not matter).
+
See 'DUP PROFILES ON A SINGLE DEVICE' for more.
See 'DUP PROFILES ON A SINGLE DEVICE' for more details.
*-m|--metadata <profile>*::
Specify the profile for the metadata block groups.
Valid values are 'raid0', 'raid1', 'raid5', 'raid6', 'raid10', 'single' or
'dup', (case does not matter).
'dup' (case does not matter).
+
A single device filesystem will default to 'DUP', unless a SSD is detected. Then
it will default to 'single'. The detection is based on the value of
A single device filesystem will default to 'DUP', unless an SSD is detected, in which
case it will default to 'single'. The detection is based on the value of
`/sys/block/DEV/queue/rotational`, where 'DEV' is the short name of the device.
+
Note that the rotational status can be arbitrarily set by the underlying block