> It sorta works.. until you get into any sort of disconnected mode.
> 
> So far, I have managed to sig11 venus on both ppc and x86, but I'm doing
> a lot better than the last time I tried coda since I haven't killed a
> server or corrupted the filestore yet ;)
> 
> The lastest crash on the x86 venus occured after messing around in a
> directory from the ppc client and having the ppc client fall over.
> 
> The last backtrace let me to believe some RPC2 thing wasn't endian-safe,
> but this makes me not so sure. Any ideas?
> 
> (gdb) bt
> #0  0x4017c116 in sigsuspend () from /lib/tls/libc.so.6
> #1  0x080c8738 in SigChoke (sig=354089116) at sighand.cc:241
> #2  <signal handler called>
> #3  0x0807509e in fsobj::Open (this=0x50a36d08, writep=0, execp=0,truncp=0,
>     cp=0x151b1e18, uid=1000) at fso.h:686
> #4  0x080c1018 in vproc::open (this=0x8390c48, cp=0x151b1e18,flags=1352887560)
>     at vproc_vfscalls.cc:223
> #5  0x080c6f03 in worker::main (this=0x8390c48) at worker.cc:1327
> #6  0x080bb516 in VprocPreamble (init_lock=0x0) at vproc.cc:146
> #7  0x40056476 in Create_Process_Part2 () at lwp.c:796
> #8  0x40057303 in L1 () at process.S:455

I just got another one of these after doing a
'cunlog; ctokens'

Should I be running the latest CVS version? 

Also, if I kill venus and restart it with 'venus -init', I wind up with
/coda mounted twice.. should we have a check in venus to unmount and
remount coda? Or should the kernel module do something different? I am
using the coda.ko module that's in 2.6.7 debian kernel packages.

Is it reasonable to have a new venus reconnect to an already-mounted
/coda? Or are we just out of luck if venus dies?