>>>> When I create a volume with only 16 characters, it works fine.  I
>>>> think there must be some padding or "reserved" space within the 32
>>>> allotted characters.  From looking at the message above (1st item
>>>> to follow) and
>>> 
>>> Right, volume replicas get ".?" siffixes and there is also possible 
>>> ".backup"
>> 
>> Ok, so it looks that the volume name has a 30 character [usable space] 
>> limitation, or a 23 character [usable space] limitation if, I assume 
>> during the volume creation process, one selects backup = y.
> 
> After some testing, I see that I assumed wrong.  When does .backup get 
> appended to the volume name in lieu of .0?  I haven't been able to create 
> a volume is such a way as to see the .backup text appended to a volume 
> name in the volume list. 

When is .backup appended? 


>> As a side note, I'd think that for use in a limited space field, 
>> something along the lines of ".bak" or even ".b" would be preferrable 
>> over ".backup".  Is this trivial to change, or would it be a
>> monumental refactor?
> 
> Obviously related to the above for determining difficulty.  Hopefully
> this is something simple enough that I can draft up a patch for --
> while I don't know that I would be up for increasing or removing the
> limitation, I should be able to manage making the volume name length
> a constant. 

Any pointers on where ".backup" gets set and how trivial it would be to 
patch to '.b'?  I don't want to undertake doing so if the general consensus 
says insanity will ensue. 


Regards,
 -Don
{void}