[OpenAFS] Re: Problems from update of openafs 1.4.12 to 1.5.77

[Andrew Deason]

On Thu, 7 Oct 2010 10:37:54 -0500
"Mike Coyne" <Mike.Coyne@PACCAR.com> wrote:

> I updated my openafs server to 1.5.77 yesterday,  this morning several
> of my volumes will not attach. This may have been due to my forgetting
> to re-compile Amanda-afs against the 1.5.77 or something completely
> different. I tried to run the salvager on the volumes but they will not
> come back on line, when I try to run vos online  I get

What does SalvageLog say when you do that?

>  I do have several backup volumes , that were created from a vos
> backupsys .  If my rw volumes are bad? How can I change/rename the
> backup volume say from home.mcoyne.backup <http://home.mcoyne.backup/>
> to home.backup as a RW volume.

I don't remember if convertROtoRW works on backup volumes... but
removing the RW volume and dumping the backup and restoring to the RW
definitely should.

> VolserverLog
> 
> Thu Oct  7 09:53:22 2010 1 Volser: GetVolInfo: Could not attach volume
> 536871386 (/vicepa:V0536871386.vol) error=101

'volinfo /vicepa 536871386' may tell you more information on wh. But
SalvageLog info I think would be most useful.

> Thu Oct  7 09:56:17 2010 FSYNC_com: from fd 21 got command 65539
> (FSYNC_VOL_NEEDVOLUME) reason 3 (SYNC_REASON_ENCODING_ERROR) pt 6
> (volumeServer) pid 8320

We probably shouldn't interpret NEEDVOLUME reason codes... that's really
misleading.

-- 
Andrew Deason
adeason@sinenomine.net