diff options
| author | Marko Hauptvogel <marko.hauptvogel@googlemail.com> | 2016-04-01 00:21:53 +0200 |
|---|---|---|
| committer | Jes Sorensen <Jes.Sorensen@redhat.com> | 2016-04-01 22:12:12 +0200 |
| commit | 95b55f18751f0d04adaec7fdddd9ccbe8cce5b18 (patch) | |
| tree | 5a5f756ac501c6b2acbfa591849116e07b4f7d8d /mdadm.8.in | |
| parent | Introduce stat2kname() and fd2kname() (diff) | |
| download | mdadm-95b55f18751f0d04adaec7fdddd9ccbe8cce5b18.tar.xz mdadm-95b55f18751f0d04adaec7fdddd9ccbe8cce5b18.zip | |
Consistent use of metric prefix in manpage
Added the optional K suffix for completeness, as it
is allowed by util.c's parse_size(char*).
Signed-off-by: Marko Hauptvogel <marko.hauptvogel@googlemail.com>
Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
Diffstat (limited to 'mdadm.8.in')
| -rw-r--r-- | mdadm.8.in | 15 |
1 files changed, 8 insertions, 7 deletions
@@ -459,7 +459,7 @@ number of spare devices. .TP .BR \-z ", " \-\-size= -Amount (in Kibibytes) of space to use from each drive in RAID levels 1/4/5/6. +Amount (in Kilobytes) of space to use from each drive in RAID levels 1/4/5/6. This must be a multiple of the chunk size, and must leave about 128Kb of space at the end of the drive for the RAID superblock. If this is not specified @@ -467,7 +467,7 @@ If this is not specified size, though if there is a variance among the drives of greater than 1%, a warning is issued. -A suffix of 'M' or 'G' can be given to indicate Megabytes or +A suffix of 'K', 'M' or 'G' can be given to indicate Kilobytes, Megabytes or Gigabytes respectively. Sometimes a replacement drive can be a little smaller than the @@ -534,7 +534,7 @@ problems the array can be made bigger again with no loss with another .B "\-\-grow \-\-array\-size=" command. -A suffix of 'M' or 'G' can be given to indicate Megabytes or +A suffix of 'K', 'M' or 'G' can be given to indicate Kilobytes, Megabytes or Gigabytes respectively. A value of .B max @@ -543,7 +543,7 @@ amount of available space is. .TP .BR \-c ", " \-\-chunk= -Specify chunk size of kibibytes. The default when creating an +Specify chunk size of kilobytes. The default when creating an array is 512KB. To ensure compatibility with earlier versions, the default when building an array with no persistent metadata is 64KB. This is only meaningful for RAID0, RAID4, RAID5, RAID6, and RAID10. @@ -551,7 +551,7 @@ This is only meaningful for RAID0, RAID4, RAID5, RAID6, and RAID10. RAID4, RAID5, RAID6, and RAID10 require the chunk size to be a power of 2. In any case it must be a multiple of 4KB. -A suffix of 'M' or 'G' can be given to indicate Megabytes or +A suffix of 'K', 'M' or 'G' can be given to indicate Kilobytes, Megabytes or Gigabytes respectively. .TP @@ -737,7 +737,7 @@ When using an bitmap, the chunksize defaults to 64Meg, or larger if necessary to fit the bitmap into the available space. -A suffix of 'M' or 'G' can be given to indicate Megabytes or +A suffix of 'K', 'M' or 'G' can be given to indicate Kilobytes, Megabytes or Gigabytes respectively. .TP @@ -808,7 +808,8 @@ an array which was originally created using a different version of which computed a different offset. Setting the offset explicitly over-rides the default. The value given -is in Kilobytes unless an 'M' or 'G' suffix is given. +is in Kilobytes unless a suffix of 'K', 'M' or 'G' is used to explicitly +indicate Kilobytes, Megabytes or Gigabytes respectively. Since Linux 3.4, .B \-\-data\-offset |