On Mon, 24 Jan 2005, Wes Chow wrote:
I was in the process of performing a vos release when I realized that one of the machines I was releasing to was off. So, I hit ctrl-C. Now AFS seems to be in an unhappy state.
[EMAIL PROTECTED]:/usr/bb $ vos listvldb bbinstall
bbinstall RWrite: 536940361 ROnly: 536940362 RClone: 536940362 number of sites -> 4 server hippo.dev.in.athenacr.com partition /vicepa RW Site -- New release -- Old release server helmsley.dev.in.athenacr.com partition /vicepa RO Site -- New release -- Old release server hippo.dev.in.athenacr.com partition /vicepa RO Site -- New release -- Old release server medula.ho.in.athenacr.com partition /vicepb RO Site -- Old release -- Old release
Partial release. Not unusual.
medula.ho.in.athenacr.com is the machine that was off when I started the release command. A subsequent vos release complained that the vldb entry was locked, so I decided to use the vos unlock command, to no avail.
It now does this:
[EMAIL PROTECTED]:/usr/bb $ vos release bbinstall Old clone is inaccessible. Try vos release -f 536940361. VOLSER: no such volume - location specified incorrectly or volume does not exist Error in vos release command. VOLSER: no such volume - location specified incorrectly or volume does not exist [EMAIL PROTECTED]:/usr/bb $ vos release -f 536940361 Failed to reclone the RW volume 536940361 Volume temporarily unavailable Error in vos release command. Volume temporarily unavailable
Wait for the volserver transaction to time out or kill (by hand, not with bos) the volserver on the (probably rw host).... but don't kill if if vos status (hostname of rw site) shows anything other than the one orphaned release.
_______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
