On Wed, 9 Feb 2000, Jan Harkes wrote:
> > 15:08:54 VGetPartition Couldn't find partition /vicepa/
> > 15:08:54 VCreateVolume: Cannot find partition /vicepa/. Bailing out.
>
> Ah now I see the problem, it is probably the trailing slash on the
> createvol_rep .... /vicepa/ that kills it. It can't figure out where to
> put the volume.
You're right. This command works, creating the volume:
createvol_rep coda_root E0000100 /vicepa
The volume is assigned ID 0x7000007.
> Let's try to get rid of the volume on the server first:
>
> volutil purge 0x7F000006 coda_root
> > /vice/vol/VRList # clean out the VRList
No luck. I get the same RPC2 problem:
root@boc:/vice/vol# volutil purge 0x7F000007 coda_root
V_BindToServer: binding to host boc.private.vovida.com
VolPurge failed with Unknown RPC2 return code 103
So it _still_ doesn't see the volume(?!)
Now I'm concerned that my files in /vice/vol may be in an inconsistent
state--but maybe they're not. ALlVolumes looks like this:
# [Last line of unsorted volume list]
coda_root.0 1000001 boc.private.vovida.com /vicepa 2 0 0 W 950139814 950139814 0
BigVolumeList looks like this:
P/vicepa Hboc.private.vovida.com T7ceb87 F7cdb46
Wcoda_root.0 I1000001 H1 P/vicepa m0 M0 U2 W1000001 C38a1fba6 D38a1fba6 B0 A0
I don't understand the formats of these or other files, so I'm at a bit
of a loss.
Shall we persevere in this way, or should I just re-install Coda "the
right way" and hope everything works? I'd like to fix this problem,
as it might contribute some new knowledge to the list, but I don't
know how well we can do it through the narrow pipe of e-mail. :(
Many thanks for your insights and suggestions so far. I still believe in
Coda and want to deploy it successfully.
> Then re-create the root volume:
> createvol_rep coda_root E0000100 /vicepa
>
> Jan
>
>
--
Quinn Weaver Software Engineer , Vovida Networks http://www.vovida.com
"I'm swingin' swords o-=*|>>>>>>>>>> ===()==========>
Strictly based on keyboards". ' --The RZA <==()==
