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.

Reviewed-on: http://gerrit.openafs.org/9408
Reviewed-by: Ken Dreyer <ktdreyer@ktdreyer.com>
Tested-by: Ken Dreyer <ktdreyer@ktdreyer.com>
(cherry picked from commit 279345c231d0a2d9f6e8c2f76a5347bafd40e70b)

Change-Id: Id273ab86bfe68f89ef629f0c4d839882852e09ab
Reviewed-on: http://gerrit.openafs.org/11126
Reviewed-by: Chas Williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
Reviewed-by: Ken Dreyer <ktdreyer@ktdreyer.com>
Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
Tested-by: Stephan Wiesand <stephan.wiesand@desy.de>

diff --git a/doc/man-pages/pod1/vos_convertROtoRW.pod b/doc/man-pages/pod1/vos_convertROtoRW.pod
index 56f71d2e7f1c56d639a8b6c2d5ba8c8b975fccb1..d0fdfb9800d186137d2e0685320fb27df5de33e2 100644 (file)
--- a/doc/man-pages/pod1/vos_convertROtoRW.pod
+++ b/doc/man-pages/pod1/vos_convertROtoRW.pod
@@ -34,6 +34,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<vos listvol>, and you
+should remove the old copy (for example, with B<vos zap>) so that the
+original file server will match the VLDB.
+
 =head1 OPTIONS
 
 =over 4