Coda File System

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

From: Jeremy Malcolm <>
Date: Mon, 17 Sep 2001 22:43:32 +0800
I'm just reposting about a problem I have mentioned about three or four
times before, but with different information because previous advice
hasn't helped and because I now have some new symptoms.  Since last
time, I've changed from ext3 to ext2 just to rule out another variable.

I've now better pinpointed the time when things start to go wrong as
being when I try to create the mountpoints of the volumes that I'm
trying to replicate over two servers.  Is there anything wrong with what
I'm doing?  (There is not much detail on points 1 to 3 because I'm
pretty sure I have those right.) - 

1. Install and start coda on server 1.
2. Install and start coda on server 2.
3. Create new replicated volumes on server 1.
4. Start venus on server 1.
5. clog as root user.
6. cd to /coda.
7. "cfs mkmount documents documents" (this is one of the volumes)

What happens is that server 1 crashes and instead of a nice mountpoint I
get a broken symlink like this:

lrw-r--r--    1 root     65534   11 Sep 17 22:15 documents -> #documents

The log shows this:

22:15:34 f_icreate: bitmap free at 0, inode 1 exists!

Assertion failed: 0, file
"/usr/src/redhat/BUILD/coda-5.3.15/coda-src/partition/ftreeifs.c", line

The mountpoint never shows up on server 2.  (If I do it the other way
around by creating the mountpoint on server 2, it "appears" to work but
it never shows up on server 1.)

It's then that venus starts refusing to start with the "CHILD: mount
system call failed. Killing parent" message and the "Failure of
coda_cnode_make for root: error -6" (or on server 1 error -110) in the
kernel.  See my previous postings for more information about that aspect
of the problem.


Providing online networks of Australian lawyers (
and Linux experts ( for instant help!
Disclaimer: GPG key: finger.
Received on 2001-09-17 10:45:15