From: Arne Wiebalck Date: Thu, 6 Dec 2012 15:23:05 +0000 (+0100) Subject: Update 'vos shadow' man page X-Git-Tag: upstream/1.6.2_pre2^2~16 X-Git-Url: https://git.michaelhowe.org/gitweb/?a=commitdiff_plain;h=cf59993d504e80f94ee1d9a56ee8b5b669810394;p=packages%2Fo%2Fopenafs.git Update 'vos shadow' man page Change the 'vos shadow' man page to say that updating the VLDB with shadow volumes does only work if the VLDB entries for the corresponding source volumes are deleted first. Reviewed-on: http://gerrit.openafs.org/8652 Tested-by: BuildBot Reviewed-by: Dan van der Ster Tested-by: Dan van der Ster Reviewed-by: Ken Dreyer (cherry picked from commit 83ccb62012d7b3b696dd48e05feb8adeb203463a) Change-Id: I59eacb7406e8bec9e5736afe32564a04be7ff72a Reviewed-on: http://gerrit.openafs.org/8786 Tested-by: BuildBot Reviewed-by: Paul Smeddle Reviewed-by: Stephan Wiesand --- diff --git a/doc/man-pages/pod1/vos_shadow.pod.in b/doc/man-pages/pod1/vos_shadow.pod.in index 385215167..32536f633 100644 --- a/doc/man-pages/pod1/vos_shadow.pod.in +++ b/doc/man-pages/pod1/vos_shadow.pod.in @@ -52,10 +52,11 @@ Using this command on a volume when the source volume is not the same as parent volume used to create the shadow will leave the destination volume in a unknown state. -Do NOT run the B or B on any fileserver -containing shadow volumes. This would update the VLDB to show all -shadowed Read/Write volumes instead of the source volumes from which -they were copied. +Running B or B on a fileserver containing +shadow volumes will not update the VLDB with the shadowed Read/Write +volumes as long as the entries for the source volumes still exist. In +a disaster recovery situation the VLDB entries for the corresponding +source volumes need hence to be deleted first. =include fragments/volsize-caution.pod