jimzah/openafs
1
0
Fork 0
mirror of https://git.openafs.org/openafs.git synced 2025-01-19 07:20:11 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 'vos shadow' man page

Browse Source 
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 <buildbot@rampaginggeek.com>
Reviewed-by: Dan van der Ster <daniel.vanderster@cern.ch>
Tested-by: Dan van der Ster <daniel.vanderster@cern.ch>
Reviewed-by: Ken Dreyer <ktdreyer@ktdreyer.com>
(cherry picked from commit 83ccb62012)

Change-Id: I59eacb7406e8bec9e5736afe32564a04be7ff72a
Reviewed-on: http://gerrit.openafs.org/8786
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Paul Smeddle <paul.smeddle@gmail.com>
Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
This commit is contained in:
Arne Wiebalck 2012-12-06 16:23:05 +01:00 committed by Stephan Wiesand
parent cddc0c4669
commit cf59993d50
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/man-pages/pod1/vos_shadow.pod.in
View File

@ -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<vos syncserv> or B<vos syncvldb> 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<vos syncserv> or B<vos syncvldb> 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