Yes, i've had a lot of problems with fossil when it gets killed. My issue was with wikifs that had some sort of memory leak i suspect, it would fill up the memory, and then fossil would crash and/or get corrupted. I had an idea for a project to use mycroftiv's rootless kernel images and have a script check whether fossil died or what, and if it did reformat it using latest venti snapshot and reopen the root, but i don't know how involved that would be. I would think -r doesn't modify the filesystem if snapshotting is turned off, but i am probably the wrong person to be asked...I currently don't even have my plan9 system installed. HTH
On Tuesday 20 April 2010 13:39:59 Adriano Verardo wrote: > John Soros wrote: > > Hello Adriano, > > Have you disabled all snapshotting features? Usiong open -r? > > How are you starting fossil, what's your configuration? > > Hi, John > > fsys main open -AWVP -c 3000 > srv fossil > srv -p fscons > > on /dev/sdD0/fossil > > open -r guarantees that fossil doesn't do physycal write at all or > prevent only user to w/create files ? > > After a fatal power down fossil complains about "metadata corruption" or > "lost 386/init" or > or the corruption of some very first logical sectors. > > adriano
