[OpenAFS-devel] problems with vos move...

[Neulinger, Nathan]

I started digging into a problem we've had with vos move for a long =
time... Occasionally on large (sometimes not) volumes, we get a failure =
in the dump. I added a bunch more debugging to the verbose vos move, and =
here is what I get:

infinity(16)>/tmp/vos move res.kumar.students afs4 a afs8 a -verbose
Locking VLDB entry for volume 536925133 ... done
Starting transaction on source volume 536925133 ... done
Allocating new volume id for clone of volume 536925133 ... done
Cloning source volume 536925133 ... done
Ending the transaction on the source volume 536925133 ... done
Starting transaction on the cloned volume 537065258 ... done
Setting flags on cloned volume 537065258 ... done
Getting status of cloned volume 537065258 ... done
Creating the destination volume 536925133 ... done
Setting volume flags on destination volume 536925133 ... done
Dumping from clone 537065258 on source to volume 536925133 on =
destination ...Failed to move data for the volume 536925133
   Possible communication failure
vos move: operation interrupted, cleanup in progress...
clear transaction contexts
Recovery: Releasing VLDB lock on volume 536925133 ... done
Recovery: Ending transaction on clone volume ...

Note - There are two problems, first, the failure in the dump (Forward), =
and second, that it is hanging when ending transaction on the cloned =
volume.=20

Unfortunately, it looks like I will have to start watching the volserver =
itself to see if I can determine the reason for the dump failure. Is it =
possible that some sort of timeout is being exceeded some how?=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216