diff options
| author | NeilBrown <neilb@suse.de> | 2009-10-29 10:11:01 +1100 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2009-10-29 10:11:01 +1100 |
| commit | d1302dd801ffa4ad8b65bee02cefa0459b0860e3 (patch) | |
| tree | 3d73b85a344d45422476337cbf23831a72954d6e /mdadm.8 | |
| parent | d28c1a73838ad808fcf6f584f83e357d2f1b3631 (diff) | |
| download | mdadm-d1302dd801ffa4ad8b65bee02cefa0459b0860e3.tar.gz mdadm-d1302dd801ffa4ad8b65bee02cefa0459b0860e3.tar.xz mdadm-d1302dd801ffa4ad8b65bee02cefa0459b0860e3.zip | |
Remove bogus warnings from man page.
LANG=C man --warnings -l mdadm.8 > /dev/null
complains that '.XX' is an invalid macro.
This is not correct. The sequence
.ig XX
anything can go here
.XX
is correct and is ignored (see 'info groff' and the 'ig' index
entry).
However the same can be achieved with
.ig
anything can go there
..
and this produces no warnings, so use that instead.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdadm.8')
| -rw-r--r-- | mdadm.8 | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -946,7 +946,7 @@ This will cause to determine the maximum usable amount of space on each device and update the relevant field in the metadata. -.ig XX +.ig .TP .B \-\-auto\-update\-homehost This flag is only meaningful with auto-assembly (see discussion below). @@ -954,7 +954,7 @@ In that situation, if no suitable arrays are found for this homehost, .I mdadm will rescan for any arrays at all and will assemble them and update the homehost to match the current host. -.XX +.. .SH For Manage mode: @@ -1429,7 +1429,7 @@ from the superblock is used to similarly create a name in .B /dev/md/ (the name will have any 'host' prefix stripped first). -.ig XX +.ig If .I mdadm cannot find any array for the given host at all, and if @@ -1447,7 +1447,7 @@ homehost tagging. The reason for requiring arrays to be tagged with the homehost for auto assembly is to guard against problems that can arise when moving devices from one host to another. -.XX +.. .SH BUILD MODE @@ -2093,7 +2093,7 @@ finds any known version of metadata. If no .I md metadata is found, the device is rejected. -.ig XX +.ig .IP + Does the metadata match an expected array? The metadata can match in two ways. Either there is an array listed @@ -2111,7 +2111,7 @@ If .I mdadm is not able to positively identify the array as belonging to the current host, the device will be rejected. -.XX +.. .I mdadm keeps a list of arrays that it has partially assembled in |