Wheeler, JF (Jonathan) wrote:
I have attempted to move a large (about 80 Gb) AFS volume from one
partition to another using the command:
vos move VOLUME MACHINE i MACHINE l
I left this running overnight and found the following error messages
when I checking this morning:
Failed to move data for volume 536871896
rxk: sealed data inconsistent
vos move: operation interrupted, cleanup in progress...
clear transaction contents
FATAL: VLDB access error: abort cleanup
cleanup complete - user verify desired result
The current situation is:
1. The volume is on-line on the source partition, but the volume (VLDB
entry) is locked. Here is the result of the command "vos listvol
MACHINE i:
Total number of volumes on server wallace partition /vicepi: 1
bfactory.vol2 536871896 RW 83886080 K On-line
Total volumes onLine 1 ; Total volumes offLine 0 ; Total busy 0
and the result of the command "vos listvldb bfactory.vol2":
bfactory.vol2
RWrite: 536871896
number of sites -> 1
server wallace.cc.rl.ac.uk partition /vicepi RW Site
Volume is currently LOCKED
2. The volume is off-line on the destination partition (same size and
same volume number). Here is the result of the command "vos listvol
MACHINE l:
Total number of volumes on server wallace partition /vicepl: 1
bfactory.vol2 536871896 RW 83886080 K Off-line
Total volumes onLine 0 ; Total volumes offLine 1 ; Total busy 0
Please note that the server is running IBM/Transarc version 3.6 (though
it may not matter in this case).
My questions are:
a) What went wrong ?
b) What chance is there that the volumes are identical ? In other
words, is it possible that I can complete the move manually ?
c) Is there anyway to compare the 2 volumes ?
Any help would be very much appreciated
I suppose your token expired over night.
The vos move command 1st creates a clone of the volume, then dumps this
clone over to the new partition. This probably takes the long time and
in this phasis your token expired.
Then the still off-line volume on the sink side should have been updated
by an incremental dump of the RW-volume on the source side.
This either could not happen any more because of the expired token or it
happened on behalf of the source side volserver whithout any new rpc
from your vos-command. But then the vldb must be updated by a ubik-call
from your vos command and that one failed. The next rpc would have
brought on-line the volume on the sink side and other rpcs would hvae
removed the volume and the clone and backup.
If the RW-volume has not been modified since the begin of the "vos move"
the off-line version on the sink side should be complete.
Hartmut Reuter
Jonathan Wheeler
e-Science Centre
Rutherford Appleton Laboratory
(cell rl.ac.uk)
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
--
-----------------------------------------------------------------
Hartmut Reuter e-mail [EMAIL PROTECTED]
phone +49-89-3299-1328
RZG (Rechenzentrum Garching) fax +49-89-3299-1301
Computing Center of the Max-Planck-Gesellschaft (MPG) and the
Institut fuer Plasmaphysik (IPP)
-----------------------------------------------------------------
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
