From 279345c231d0a2d9f6e8c2f76a5347bafd40e70b Mon Sep 17 00:00:00 2001 From: Ken Dreyer Date: Wed, 6 Mar 2013 13:53:29 -0700 Subject: [PATCH] doc: recommend cleanup steps in "vos convertROtoRW" man page vos convertROtoRW leaves the older RW copy on the original fileserver, although it is no longer in the VLDB. Provide the user with some hints regarding clean up. Change-Id: I5f6fcf7d5a516b59438d84e60f163a567d3a64fd Reviewed-on: http://gerrit.openafs.org/9408 Reviewed-by: Ken Dreyer Tested-by: Ken Dreyer --- doc/man-pages/pod1/vos_convertROtoRW.pod.in | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/man-pages/pod1/vos_convertROtoRW.pod.in b/doc/man-pages/pod1/vos_convertROtoRW.pod.in index c19e7b4..fad6545 100644 --- a/doc/man-pages/pod1/vos_convertROtoRW.pod.in +++ b/doc/man-pages/pod1/vos_convertROtoRW.pod.in @@ -38,6 +38,12 @@ failed server, or accidental deletion. The command name is case-sensitive. It must be issued with the capital "RO" and "RW". +After running vos convertROtoRW, the old file server will still contain +the old Read/Write copy of the volume, even if the VLDB no longer +references it. You can view the old volume with B, and you +should remove the old copy (for example, with B) so that the +original file server will match the VLDB. + =head1 OPTIONS =over 4 -- 1.9.4