From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Soros <sorosj@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Date: Tue, 20 Apr 2010 14:18:33 +0200
User-Agent: KMail/1.13.2 (Linux/2.6.33-gentoo-1; KDE/4.4.2; i686; ; )
References: <4BCD85B5.1060404@tecmav.com> <201004201313.41351.sorosj@gmail.com>
	<4BCD928F.4030702@tecmav.com>
In-Reply-To: <4BCD928F.4030702@tecmav.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201004201418.36176.sorosj@gmail.com>
Subject: Re: [9fans] Fossil robustness
Topicbox-Message-UUID: 09f3d166-ead6-11e9-9d60-3106f5b1d025

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