On Mon, Aug 1, 2011 at 10:59 AM, Andrew Deason <adea...@sinenomine.net> wrote: > On Mon, 1 Aug 2011 10:45:42 -0400 > Derrick Brashear <sha...@gmail.com> wrote: > >> > I can't, because as mentioned the volume name is also associated >> > with another volume id that I definitely don't want to delete. To >> > illustrate what I mean, 130.85.24.58 is the server I want to delete >> > and the RO volume associated with it that I want to delete is named >> > g.ilin22.local: > > Well, your vldb is mildly broken, then. Do you know how the other volume > got created? Our volume creation tools should prevent you from > duplicating a volume name.
wild guess: restored ro to alternate id while the rw had no clone; failed removal, later clone of rw. alternately: that was the old id for the ro and a restore later was done to that id because that ued to be the id before deletion. but yes, we should save you from that. > And 'vos delentry' doesn't delete volumes. You could just 'vos delentry' > the volume twice, and presumably that will get rid of the 'bad' one. > Afterwards, you can run syncserv/syncvldb/'addsite -valid' to get the > entry back for the 'good' one. and that's probably the simplest answer. -- Derrick _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
