Hi, Subsequent to some discussion on this list, I decided to try setting up a vent-backed fossil file system. I did this straight from the 4th Ed. install CD. The system booted from the HDD and seemed to start up and shut down fine. Then, one evening I used Acme to take some notes. At about 05:00, I was bragging to a buddy of mine how cool Plan 9 was. No sooner than I began to show him Acme's nifty chording, did the rio window began filling up with error messages about trouble writing to the hard drive. Although rio kept running, the file system hung. Not being able to recover the system, I rebooted it. Well, I tried to. The boot process didn't get very far. Ever since then, every time I try to boot it, the kernel panics. (Messages below.)
If I knew anything about how the root filesystem was brought online during boot, I might be able to debug this myself. Alas, I have no idea which programs are generating which parts of this output, so I really have no angle from which to attack the problem. Any ideas? The P9 partition is the third primary partition on the disk. I'm fairly sure the HDD is good, because I tested it before the install, and have installed and run Linux on the same HDD without incident. Although I started and shut down Plan 9 a number of times (just to test its range of motion), this crash occurred the first time I tried saving any data to the file system (a text file under /usr/glenda/). Any help would be much appreciated! Here's what the console shows (typed by hand, may be typos): root is from (tcp, local)[local!#S/sdC0/fossil]: user[none]: glenda time... venti...2011/0318 00:24:56 venti: conf.../boot/venti: mem 6,252,817 bcmem 12,505,634 icmem 18,758,451...httpd tcp!127.1!8000...init...icache 18,758,451 bytes = 293,101 entries; 4 scache sync...2011/0318 00:24:56 arenas00: indexing 45372 clumps... announce tcp!127.1!17034...serving. fossil(#S/sdC0/fossil)...fsys: dialing venti at tcp!127.1!17034 /boot/fossil: labelUnpack: bad label: 0xcb 0xb2 0x3d22d532 0x8cacb517 0xfc0d00cb /boot/fossil: fsOpen error fsOpen: corrupted block label fsys main open -c 3000: fsOpen: corrupted block label fsys: 'main' not open fsys main snaptime -s 60 -a 0500 -t 2880: fsys 'main' not open version...boot: mount /: fsys: 'main' not open panic: boot process died: unknown panic: boot process died: unknown dumpstack disabled cpu0: exiting -- +---------------------------------------------------------------+ |E-Mail: smi...@zenzebra.mv.com PGP key ID: BC549F8B| |Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B| +---------------------------------------------------------------+
