btrfs-progs: docs: add raid1c34 profiles to balance convert
The extended raid1 profiles are missing from the list. Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
parent
2910ca8009
commit
2aeaea41a8
|
@ -216,10 +216,10 @@ For example, this means that we can convert metadata chunks the "hard" way
|
|||
while converting data chunks selectively with soft switch.
|
||||
|
||||
Profile names, used in 'profiles' and 'convert' are one of: 'raid0', 'raid1',
|
||||
'raid10', 'raid5', 'raid6', 'dup', 'single'. The mixed data/metadata profiles
|
||||
can be converted in the same way, but it's conversion between mixed and non-mixed
|
||||
is not implemented. For the constraints of the profiles please refer to `mkfs.btrfs`(8),
|
||||
section 'PROFILES'.
|
||||
'raid1c3', 'raid1c4', 'raid10', 'raid5', 'raid6', 'dup', 'single'. The mixed
|
||||
data/metadata profiles can be converted in the same way, but it's conversion
|
||||
between mixed and non-mixed is not implemented. For the constraints of the
|
||||
profiles please refer to `mkfs.btrfs`(8), section 'PROFILES'.
|
||||
|
||||
ENOSPC
|
||||
------
|
||||
|
|
|
@ -51,7 +51,7 @@ suitable as default.
|
|||
*-m|--metadata <profile>*::
|
||||
Specify the profile for the metadata block groups.
|
||||
Valid values are 'raid0', 'raid1', 'raid1c3', 'raid1c4', 'raid5', 'raid6',
|
||||
'gaid10', 'single' or 'dup' (case does not matter).
|
||||
'raid10', 'single' or 'dup' (case does not matter).
|
||||
+
|
||||
Default on a single device filesystem is 'DUP', unless an SSD is detected, in which
|
||||
case it will default to 'single'. The detection is based on the value of
|
||||
|
|
Loading…
Reference in New Issue