[OpenAFS] vos move "forgot" to remove .backup volume.
Fri, 13 Mar 2009 19:22:21 -0400
On Fri, Mar 13, 2009 at 7:16 AM, Harald Barth <email@example.com> wrote:
> In the volser log, I have a lot of messages like this:
> Fri Mar 13 02:47:06 2009 trans 248 on volume 537084431 is older than XXXX seconds
> which end at XXXX = 7350. After that silence in the logfile.
> So is there some assumption in vos that this transaction can not take
> longer than X and is the silently aborted?
IIRC all vos transactions are supposed to time out after a fixed
length of time. I thought it was supposed to tell you it gave up,
though. [I can't find my copy of the AFS src code on this laptop. Who
ate my copy of the source code? Dammit. I'm redownloading it on the
World's Slowest Network. I swear, there are carrier pigeons involved.]
> Some info about the volume: diskused: 9250606KB, filecount: 2145921,
> space used in vicepa ~13GB.
Come on, Haba, you've been to this party before -- what version of OpenAFS?
> Should I add something to my volume move script that actually checks
> if a .backup is really gone after a vos move?
a) a bug
b) a problem with your system
c) space aliens dancing on your server
Have you done some trace or tcpdump program to see what the vos
command is doing?
Have you identifed that the transaction in question that's lingering
is a delete? 'vos status' (and maybe 'ps') should identify it.
> PS, trivia: trevally is a fish and valine is an amino acid.
"And the capital of Nebraska is Lincoln!"