Coda File System

Re: problem with "coda.o"

From: Jan Harkes <>
Date: Fri, 19 Nov 1999 11:05:51 -0500
On Fri, Nov 19, 1999 at 10:31:05AM -0500, Vidyamani Parkhe wrote:
> I cannot start the server error message:
> Cant't open Log Device: No such file or directory 
> I zeroed down to tha fact that the "coda" module was not very well
> setup !

That would be pretty dumb server error. The server has got nothing to do
with the coda.o kernel module. coda.o simply bounces filesystem requests
back to the Coda-_client_.

> as suggested i the HOW-TO manuals ... i tried to insert the mod as 
> insmod coda.o
> but the following error occurs:
> coda.o: init_module:Device and resource busy.

Either, there is already a module loaded, or something else is wrong,
check the output of dmesg and /var/log/messages to see what the kernel
is complaining about.

> I think there is where the problem lies .... 

Not for starting a server. It is more likely that something went wrong
with vice-setup during the initialization of the RVM log and data

> also, the local client does not seem to get connected to the local
> server - also the "lsmod" command does not output an entry on "coda"

.... Is the server running? ....
.... If the kernel spits out the module loaded by insmod, how can the
Coda client, venus, make the kernel accept it? ....

>  Error message:
> GetRootVolume: can't get root volume name !

.... Is the server running? ....


ps. sorry for the `abruptness' of my questions, been a long night..
Received on 1999-11-19 11:08:55