Coda File System

Re: "Assertion failed" in cfs mkmount is what leads to venus error -6

From: Jeremy Malcolm <Jeremy_at_Malcolm.wattle.id.au>
Date: Tue, 18 Sep 2001 09:49:18 +0800
OK thanks, at least that worked!  So now I know whenever reinstalling
coda I have to delete the whole /vicepa and /vice directories
(previously I had just been deleting FTREEDB from /vicepa).  But now I
am back to the same infuriating problem, or combination of problems,
that I had originally (see
http://www.coda.cs.cmu.edu:80/maillists/codalist-2001/0689.html.

I won't repeat that previous post here because it is all still
applicable but the nub of it is that I get "connection timed out" or
"input/output error" whenever I try to do anything with the mounted
volumes.  Then after I stop and restart the server and client, from that
point on venus crashes with "CHILD: mount system call failed. Killing
parent."  dmesg shows:

No pseudo device in upcall comms at d085b4e4 [this multiple times]
Coda: Bye bye.
coda_read_super: rootfid is (0x7f000000,0x1,0x1)
Failure of coda_cnode_make for root: error -6

/vice/srv/SrvLog shows:

09:20:03 client_GetVenusId: got new host 192.168.0.1:2430
09:20:03 Building callback conn.
09:20:03 No idle WriteBack conns, building new one
09:20:03 Writeback message to 192.168.0.1 port 2430 on conn 1ab82fa6
succeeded
09:20:03 RevokeWBPermit on conn 1ab82fa6 returned 0
09:20:03 ValidateVolumes: 0x7f000000 failed!
09:20:03 GetVolObj: VGetVolume(7f000000) error 103
09:20:03 GrabFsObj, GetVolObj error Volume not online
09:25:12 client_GetVenusId: got new host 192.168.0.20:2430
09:25:12 Building callback conn.
09:25:12 No idle WriteBack conns, building new one
09:25:12 Writeback message to 192.168.0.20 port 2430 on conn 32604a4
succeeded
09:25:12 ValidateVolumes: 0x7f000000 failed!

7f000000 is the non-replicated root volume, which I am not using, but I
am creating just because trying to create a replicated root volume
seemed to get me into an even bigger mess.  The four replicated volumes
are mounted inside /coda.  Is there something wrong with doing this?  Do
I need to create a separate mount point for the root volume?

TIA

-- 
JEREMY MALCOLM <Jeremy@Malcolm.wattle.id.au> http://malcolm.wattle.id.au
Providing online networks of Australian lawyers (http://www.ilaw.com.au)
and Linux experts (http://www.linuxconsultants.com.au) for instant help!
Disclaimer: http://www.terminus.net.au/disclaimer.html. GPG key: finger.
Received on 2001-09-17 21:51:34