Greetings all: 

I have been using the following wiki for keeping abreast of coda 
limitations:
http://coda.wikidev.net/Limitations 

One of the limitations listed is volume name length, which is supposedly 32 
characters.  However, when I create a volume name 32 characters long, it 
always fails with an "Unknown RPC2 return code 700": 

# /vice/bin/createvol_rep 0123456789abcdef0123456789abcdef `hostname -f`
Replicated volumeid is xxxxxxxx
creating volume 0123456789abcdef0123456789abcdef.0 on `hostname -f` 
(partition /vice/pa)
V_BindToServer: binding to host `hostname -f`
V_BindToServer: binding to host `hostname -f`
Set Log parameters
Fetching volume lists from servers:
V_BindToServer: binding to host `hostname -f`
GetVolumeList finished successfully
`hostname -f` - success
V_BindToServer: binding to host `hostname -f`
VLDB completed.
<echo 0123456789abcdef0123456789abcdef xxxxxxxx 1 xxxxxxxx 0 0 0 0 0 0 0 >> 
/vice/db/VRList.new>
V_BindToServer: binding to host `hostname -f`
VolMakeVRDB failed with Unknown RPC2 return code 700
Failed to create a new VRDB file from /vice/db/VRList.new 


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 
getvolumelist output (2nd item to follow), I believe the padding amounts to 
between 1 to 3 characters: 

creating volume 0123456789abcdef0123456789abcdef.0 on `hostname -f` 

('.0' ammended to the end) 

and 

W0123456789abcdef0123456789abcde Ixxxxxxx Hx P/vice/pa mx Mx Ux Wxxxxxxx 
Cxxxxxxxx Dxxxxxxxx Bx Ax 

('W' ammended to the beginning -- since the end is truncated, it is unclear 
whether it ends truncated, ends in 'f', or ends in 'f.0' raising the 
additional question of whether the 'f' or 'f.0' is necessary for internal 
volume naming) 


Regardless, has anyone else noticed this, or is it some bizarre issue with 
my setup? 


Regards,
 -Don
{void}