[OpenAFS] vldb hosed, lists no volumes

[J. Maynard Gelinas]

   Nope. A vos syncserv claims to syncronize, but listvldb doesn't show
any of my original volumes. vos listvol continues to show volume names,
disk consumption, etc. Note that I'm doing a vos syncserv hostname
partition. A vos syncvldb hostname partition volumename claims the volume
is syncronized but then a vos listvldb doesn't show the entry. A vos
examine volumename then claims there is "no such entry".

Thanks though,
--Maynard

On Tue, 5 Mar 2002, Derrick J Brashear wrote:

> On Tue, 5 Mar 2002, J. Maynard Gelinas wrote:
>
> >
> >    when performing a vos listvldb. This happened while bringing up a new
> > fileserver/vlserver/ptserver and entering a mistaken vos syncvldb. Whoops,
>
> any reason you can just use vos syncserv to recover now?
>
> > now the original server has an empty vldb cloned from the new volume
> > server. Fortunately, we're not in production yet. However, a vos listvols
> > lists all the volumes which were previously in the vldb, and the vice
> > partition which houses the data still appears to contain something. I've
> > been poking around the documentation trying to figure out how to restore
> > the volumes short of restoring from tape. I've tries a bos salvage, but no
> > luck. Is there any way I can specify a volume listed in listvols and
> > assign it to a specific partition and host to create a new vldb entry
> > without destroying the original data?
> >
> > Thanks,
> > --Maynard
> >
> > _______________________________________________
> > OpenAFS-info mailing list
> > OpenAFS-info@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-info
> >
>