(Illustration by Gaich Muramatsu)
I'm trying to set up a brand new system with Coda, and having some problems. I have the Coda client installed, and Venus can access testserver.coda.cs.cmu.edu just fine. I am now trying to set up a Coda server on the same machine. Starting from a clean system, I ran the vice-setup script, placing the DATA and LOG partitions in separate raw disk partitions. (20M log and 200M data) /vicepa holds the files, and it's mounted on a 4gb ext2fs. I ran createvol_rep root E0000100 /vicepa I then configured Venus to use my local server, started it up, and received the following messages: Coda Venus, version 5.3.7 Date: Thu 05/18/2000 21:09:50 /usr/coda/LOG validated at size 0x288a00 21:09:50 /usr/coda/DATA validated at size 0xa211dc 21:09:50 loading recoverable store 21:09:51 Last init was Thu May 18 20:46:10 2000 21:09:51 Last shutdown was clean 21:09:51 starting VSGDB scan 21:09:51 1 vsg entries in table 21:09:51 0 vsg entries on free-list 21:09:51 starting VDB scan 21:09:51 2 vol entries in table (0 MLEs) 21:09:51 0 vol entries on free-list (0 MLEs) 21:09:51 starting FSDB scan (4166, 100000) (25, 75, 4) 21:09:51 fatal error -- fsobj::Recover: bogus VnodeType (0) 21:09:51 RecovTerminate: clean shutdown Assertion failed: 0, file "fso1.cc", line 527 Sleeping forever. You may use gdb to attach to process 905. Assertion failed: 0, file "venusrecov.cc", line 635 Sleeping forever. You may use gdb to attach to process 905. Any suggestions on how I might cure this? I'm running under RedHat 6.2, using the coda.o module supplied by RH. Tom Goltz Software Engineering Services (603) 594-9922 (603) 594-9939 (fax)Received on 2000-05-19 10:44:14