[OpenAFS] Unable to 'move' volume....volume ID too large / cloned volume not findable?

Rainer Toebbicke rtb@pclella.cern.ch
Fri, 20 Mar 2009 15:53:07 +0100

Hartmut Reuter schrieb:

> Yes, of course, but what error changed the MaxVolumeId in the vleserver
> is still completely unclear. BTW also we had a giant jump in the volume
> ids some years ago, but fortunately it was not big enough to reach the
> sign bit.
> Hartmut

Me too! Here, here!!

Last year we started a gigantic "backup volrestore" (not diskrestore) after a 
double disk failure in a RAID 5.

Very early in the process the maximum volume ID went from the usual 530-odd 
million to 1.9 billion. No obvious bit pattern in sight, and no obvious place 
where this could have gone wrong, and of course "backup volrestore" has been 
seen getting that right already. I even knew *when* it had happened with a 
precision of about 1 minute, but that didn't help.

Being a bit nostalgic I thought about zapping the VLDB to something in the 
traditional range again, apart from this bug the possibility that we ever 
overrun numbers of the new "family" is pretty remote...

Rainer Toebbicke
European Laboratory for Particle Physics(CERN) - Geneva, Switzerland
Phone: +41 22 767 8985       Fax: +41 22 767 7155