(Illustration by Gaich Muramatsu)
I was writing a bunch of stuff out to the coda directory, and the client (linux 2.1.123, included coda.o, coda 4.6.6) died. Now, when I start venus, I can see the files that were being copied into /coda, but none of the stuff on the remote side. Eventually, I get something like this: 12:16:44 Fatal Signal (11); pid 25195 becoming a zombie... 12:16:44 You may use gdb to attach to 25195 The stack trace looks like this: #0 0x400d9a54 in () #1 0x400fc40c in h_nerr () #2 0x80eafdc in FatalSignal (sig=11, code=0, contextPtr=0x0) at sighand.cc:397 #3 0x80eac14 in SEGV (sig=11, code=0, contextPtr=0x0) at sighand.cc:230 #4 <signal handler called> #5 0x4013aad0 in ?? () #6 0x813ff07 in vproc_iterator::operator() (this=0x15110e68) at vproc.cc:803 #7 0x80e806e in mariner_iterator::operator() (this=0x15110e68) at mariner.cc:611 #8 0x80e6eec in MarinerLog (fmt=0x8227ef5 "store::reintegrate done\n") at mariner.cc:212 #9 0x811e756 in ClientModifyLog::COP1 (this=0x214616cc, buf=0x839f288 "", bufsize=19580, UpdateSet=0x15111ed4) at vol_cml.cc:2300 #10 0x812e1c8 in volent::IncReintegrate (this=0x2146160c, tid=-118) at vol_reintegrate.cc:297 #11 0x812db51 in volent::Reintegrate (this=0x2146160c) at vol_reintegrate.cc:151 #12 0x812f4ec in reintegrator::main (this=0x8334a90, parm=0x813e670) at vol_reintegrate.cc:736 #13 0x813e777 in VprocPreamble (init_lock=0x8334b70) at vproc.cc:173 #14 0x817d345 in Create_Process_Part2 () at lwp.c:1107 #15 0x8180077 in () at rec_dlist.cc:381 #16 0x805304ec in ?? () Is there a way to recover from this (besides wiping the client and starting over?) Or is there anything else I could do that would be useful? Mike StoneReceived on 1998-10-24 12:30:23