[OpenAFS] Re: vos syncvldb error
Wed, 02 Dec 2009 14:43:15 -0500
Andrew Deason wrote:
> On Wed, 2 Dec 2009 12:44:09 -0600
> Andrew Deason <firstname.lastname@example.org> wrote:
>> On Wed, 02 Dec 2009 13:27:40 -0500
>> Wenping Yang <email@example.com> wrote:
>>> with -verbose flag, it didn't give any more info for 536870944
>>> except this:
>>> [root@psrwjmsafs1 logs]# vos syncvldb psrwjmsafs1 -verbose |grep
>>> 536870944 VLDB: volume entry exists in the vldb
>>> Could not create a VLDB entry for the volume 536870944
>> The interesting part of the -verbose output is about the previous ten
>> lines before these. Don't just grep; save the output to a file, and
>> see what output is around these lines. Or post the full output
>> somewhere else and link it here (or send it to me in private email,
>> if you want).
> (sent to me off-list; thanks)
> So, 536870945 on that server is marked as an RO volume with 536870944 as
> its RW parent, even though 536870944 doesn't exist. But a volume with
> the same name as that RW does already exist (536870947), which is why
> you get the 'VLDB entry exists' error. (syncvldb tries to create a new
> entry for 536870944 with 536870945 as an rosite)
> I'd be a little curious to see what 'vos listvl 536870945' outputs.
> However, the solution is probably just to 'vos remove psrwjmsafs1 e
> 536870945'. If you do indeed want a readonly volume for that data, just
> create a new rosite for 536870947 and release it.
Output of 'vos listvl 536870945' is 'VLDB: no such entry'.
After delete 536870945, 'vos syncvldb' is successful.
Thanks to you and Antoine for your help.