Update the default superblock type when passing just '1' in the man page
as it was incorrect according to the man page versus what was actually happening.
This commit is contained in:
parent
d00f539784
commit
40a50da058
@ -1,5 +1,14 @@
|
||||
--- a/mdadm.8.in
|
||||
+++ b/mdadm.8.in
|
||||
--- mdadm-3.2.2/mdadm.8.in.man 2011-06-17 01:15:50.000000000 -0400
|
||||
+++ mdadm-3.2.2/mdadm.8.in 2011-07-14 20:18:49.240997107 -0400
|
||||
@@ -336,7 +336,7 @@ It can easily be moved between hosts wit
|
||||
recovery operation can be checkpointed and restarted. The different
|
||||
sub-versions store the superblock at different locations on the
|
||||
device, either at the end (for 1.0), at the start (for 1.1) or 4K from
|
||||
-the start (for 1.2). "1" is equivalent to "1.0".
|
||||
+the start (for 1.2). "1" is equivalent to "1.2".
|
||||
'if '{DEFAULT_METADATA}'1.2' "default" is equivalent to "1.2".
|
||||
.IP ddf
|
||||
Use the "Industry Standard" DDF (Disk Data Format) format defined by
|
||||
@@ -706,7 +706,7 @@ facts the operator knows.
|
||||
When an array is resized to a larger size with
|
||||
.B "\-\-grow \-\-size="
|
||||
@ -9,7 +18,7 @@
|
||||
.B \-\-assume\-clean
|
||||
can be used with that command to avoid the automatic resync.
|
||||
|
||||
@@ -811,6 +811,11 @@ number, and there is no entry in /dev for that number and with a
|
||||
@@ -811,6 +811,11 @@ number, and there is no entry in /dev fo
|
||||
non-standard name. Names that are not in 'standard' format are only
|
||||
allowed in "/dev/md/".
|
||||
|
||||
@ -97,7 +106,7 @@
|
||||
.BR <ignore> )
|
||||
it will look through the available devices for possible arrays and
|
||||
will try to assemble anything that it finds. Arrays which are tagged
|
||||
@@ -2200,11 +2205,11 @@ change the "size" attribute for RAID1, RAID4, RAID5 and RAID6.
|
||||
@@ -2200,11 +2205,11 @@ change the "size" attribute for RAID1, R
|
||||
.IP \(bu 4
|
||||
increase or decrease the "raid\-devices" attribute of RAID0, RAID1, RAID4,
|
||||
RAID5, and RAID6.
|
||||
@ -112,7 +121,7 @@
|
||||
.IP \(bu 4
|
||||
add a write-intent bitmap to any array which supports these bitmaps, or
|
||||
remove a write-intent bitmap from such an array.
|
||||
@@ -2250,7 +2255,7 @@ space to start being used. If the size is increased in this way, a
|
||||
@@ -2250,7 +2255,7 @@ space to start being used. If the size
|
||||
are synchronised.
|
||||
|
||||
Note that when an array changes size, any filesystem that may be
|
||||
@ -130,7 +139,7 @@
|
||||
|
||||
.SS RAID\-DEVICES CHANGES
|
||||
|
||||
@@ -2435,8 +2440,8 @@ must match one of the names or patterns in a
|
||||
@@ -2435,8 +2440,8 @@ must match one of the names or patterns
|
||||
line.
|
||||
|
||||
.IP +
|
||||
@ -141,7 +150,7 @@
|
||||
.B \-\-metadata
|
||||
or
|
||||
.B \-e
|
||||
@@ -2467,6 +2472,7 @@ is not able to positively identify the array as belonging to the
|
||||
@@ -2467,6 +2472,7 @@ is not able to positively identify the a
|
||||
current host, the device will be rejected.
|
||||
..
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
Summary: The mdadm program controls Linux md devices (software RAID arrays)
|
||||
Name: mdadm
|
||||
Version: 3.2.2
|
||||
Release: 3%{?dist}
|
||||
Release: 4%{?dist}
|
||||
Source: http://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-%{version}.tar.bz2
|
||||
Source1: mdmonitor.init
|
||||
Source2: raid-check
|
||||
@ -125,6 +125,10 @@ fi
|
||||
%{_initrddir}/*
|
||||
|
||||
%changelog
|
||||
* Thu Jul 14 2011 Doug Ledford <dledford@redhat.com> - 3.2.2-4
|
||||
- Fix minor issue in man page
|
||||
- Resolves: bz717795
|
||||
|
||||
* Thu Jul 07 2011 Milan Broz <mbroz@redhat.com> - 3.2.2-3
|
||||
- Use unit files with systemd. (johannbg)
|
||||
- Add sub-package sysvinit for SysV init script.
|
||||
|
Loading…
Reference in New Issue
Block a user