From d1302dd801ffa4ad8b65bee02cefa0459b0860e3 Mon Sep 17 00:00:00 2001 From: NeilBrown Date: Thu, 29 Oct 2009 10:11:01 +1100 Subject: 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 --- mdadm.8 | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/mdadm.8 b/mdadm.8 index 676a9cd..d79f660 100644 --- a/mdadm.8 +++ b/mdadm.8 @@ -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 -- cgit v1.2.1 From 5bac0443e0223bb8668744a1f191f3f14eb0b89c Mon Sep 17 00:00:00 2001 From: Marco d'Itri Date: Thu, 29 Oct 2009 10:14:43 +1100 Subject: vol_id was removed by the udev upstream maintainer in May 2009. One should use /sbin/blkid -o udev -p ... (from util-linux >> 2.16) instead of vol_id --export ... Author: Marco d'Itri Bug-Debian: http://bugs.debian.org/541884 Reviewed-by: martin f. krafft Signed-off-by: NeilBrown --- udev-md-raid.rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/udev-md-raid.rules b/udev-md-raid.rules index 300a754..c9a4f0e 100644 --- a/udev-md-raid.rules +++ b/udev-md-raid.rules @@ -30,7 +30,7 @@ ENV{DEVTYPE}=="partition", ENV{MD_UUID}=="?*", SYMLINK+="disk/by-id/md-uuid-$env ENV{DEVTYPE}=="partition", ENV{MD_DEVNAME}=="*[^0-9]", SYMLINK+="md/$env{MD_DEVNAME}%n" ENV{DEVTYPE}=="partition", ENV{MD_DEVNAME}=="*[0-9]", SYMLINK+="md/$env{MD_DEVNAME}p%n" -IMPORT{program}="vol_id --export $tempnode" +IMPORT{program}="/sbin/blkid -o udev -p $tempnode" OPTIONS+="link_priority=100" ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}" ENV{ID_FS_USAGE}=="filesystem|other", ENV{ID_FS_LABEL_ENC}=="?*", SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}" -- cgit v1.2.1