It appears that I *do* have a root volume:
(I recall creating it, so that's good)

/vice/vol/VolumeList
+++
P/vicepc Hserv1.penguinboots.com T13b676 F13a631
Wcoda:root.0 I1000001 H1 P/vicepc m0 M0 U2 W1000001 C3878cb1a D3878cb1a B0 A0
+++

/vice/vol/VRList
+++
coda:root 7F000000 1 0 0 0 0 0 0 0 E0000100
+++

And recreating a root volume (as you suggested) is fruitless: it already exists
in VRList, so coda will not allow it.

It seems to me that things are failing on the CLIENT side, I don't think the
server is the problem ...

Any other ideas?
Brice

Jan Harkes wrote:

> On Sun, Jan 09, 2000 at 10:05:15AM -0600, Brice Ruth wrote:
> > Greets,
> >
> > I recently setup CODA and succeeded in setting up the server
> > (apparently), however - venus setup on my client reports:
> >
> > 10:02:12        0 hdb entries on free-list
> > >>10:02:12 Kernel version ioctl failed (Inappropriate ioctl for device)!<<
> > >>10:02:12 2.3 or later kernels require an updated kernel module!<<
> > 10:02:12 Initial LRDB allocation
> > 10:02:12 Getting Root Volume information...
> > >>10:02:13 GetRootVolume: can't get volinfo for root volume (coda:root)!<<
> >
> > The lines encapsulated in >><< are the problem ... I don't understand
> > what's going on.  I had Coda server/client running previously on
> > 2.2.13/2.2.12 (server/client, respectively) and it seemed fine.
>
> Kernel module is fine, it looks like we actually will not end up having
> a different kernel-API with 2.3 kernels after all. Some important VFS
> changes are being introduced in the 2.3 kernels which will make Coda's
> life a lot simpler.
>
> Are you testing against your own server? Did you create the root volume
> on the server?
>
> /vice/vol/Volumelist and /vice/vol/VRList should have entries for
> coda:root. Otherwise check whether the server crashed on startup, or
> rerun 'createvol_rep coda:root E0000001 /vicepa'
>
> Jan

--
+--+
"The use of COBOL cripples the mind; its teaching should,
therefore, be regarded as a criminal offense."
-- E. W. Dijkstra (1982)