[OpenAFS] vos examine oddity

[Matthew N. Andrews]

Would this perhapse happen in the case where the RW site had been moved 
to that partition after the RO volume there already existed? what about 
it being restored there from backup? just guessing here, but seems possible.

-Matt


Russ Allbery wrote:
> Dexter 'Kim' Kimball <dhk@ccre.com> writes:
> 
> 
>>In this case I'm explicitly examining an RO.  The ID of the RO is
>>correctly reported 536901459 on the <volume name> line -- but in that
>>same record two lines down the RO volID is "0"
> 
> 
>>So apparently vos exa does know the RO volID (first line) but it doesn't
>>get printed (third line) because (beats me ... called from different
>>routine?  gets reset somewhere after it's first populated? elves?)
> 
> 
> Yeah, this is the same issue.  The reason why the last part is correct is
> that that information is coming from the VLDB instead of the volserver.
> It looks like the volserver sometimes doesn't know that there's a RO.
> 
> I'm going to file a bug with the OpenAFS bug tracker.  It's not a big deal
> for us, as I can still do what I needed to do by inverting the sense of my
> query (look for ROs and then find their RWs via the RWrite part, which
> appears to always be okay).
>