On 3/7/2019 11:59 AM, Susan Litzinger wrote: > Hmm.. I moved removed the incorrect RO and created a new RO on velma, > then tried to 'release' the new one prior to moving it to a different > server and that doesn't work. I'm hesitant to go ahead and move it if > it's not in a good state.
"vos remsite" only modifies the location database. It does not remove volumes from vice partitions. You needed to execute "vos remove" not "vos remsite". You are still receiving the EXDEV error from velma because there are still two vice partitions attached to velma each of which have a volume from the same volume group. The fact that you were able to get into this situation is due to bugs in OpenAFS which were fixed long ago in AuriStorFS. To cleanup: vos remove -server vlema.psc.edu -partition vicepcb -id 537176385 and then vos release -id root.cell If you are still seeing errors, examine the VolserLog on velma.psc.edu and use vos listvol -server velma.psc.edu -fast | grep 537176385 to see if there are stranded readonly volumes left on somewhere. Jeffrey Altman
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
