[OpenAFS] vos move "forgot" to remove .backup volume.
Mon, 16 Mar 2009 10:00:13 +0100
I'd dare the conjecture that creating the transaction in the volserver failed,
possibly because some other transaction such as a trivial "vos listvol" was
going on, and "vos move" forgot to tell you about it.
As we do frequent "vos listvols" on all our servers for monitoring we used to
see problems with that, for example during the nightly "vos backupsys".
I'll submit a patch as it is generally useful - the brutal rather than the
elegant approach: sleep and retry a couple of times in NewTrans(). It got
delayed a bit as it corrected a locking problem as well in 1.4.6 still which
collided with the correction of that problem in 1.4.8.
But it's a conjecture anyway: there may still be something else.
Harald Barth schrieb:
> A normal vos move looks like this:
> vos move prj.sbc.abernsel13 trevally a valine a -v -local
> Creating transaction for backup volume 537080987 on source ... done
> Setting flags on backup volume 537080987 on source ... done
> Deleting the backup volume 537080987 on the source ... done
> Ending transaction on backup volume 537080987 on source ... done
> vos move prj.sbc.aronh09 trevally a valine a -v -local
> Creating transaction for backup volume 537084431 on source ... done
> Starting transaction on the cloned volume 537097246 ... done
> Deleting the cloned volume 537097246 ... done
> Ending transaction on cloned volume 537097246 ... done
> Volume 537084429 moved from trevally /vicepa to valine /vicepa
> Here we have the "Creating transaction for backup volume ..." but then
> the backup volume does not occur in the output from vos move any more.
> And it is left:
> # vos listvol trevally
> Total number of volumes on server localhost partition /vicepa: 5
> prj.sbc.aronh09.backup 537084431 BK 9250606 K On-line
European Laboratory for Particle Physics(CERN) - Geneva, Switzerland
Phone: +41 22 767 8985 Fax: +41 22 767 7155