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 13:13:38 +0200
User-Agent: KMail/1.13.2 (Linux/2.6.33-gentoo-1; KDE/4.4.2; i686; ; )
References: <4BCD85B5.1060404@tecmav.com>
In-Reply-To: <4BCD85B5.1060404@tecmav.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201004201313.41351.sorosj@gmail.com>
Subject: Re: [9fans] Fossil robustness
Topicbox-Message-UUID: 09ca45da-ead6-11e9-9d60-3106f5b1d025

Hello Adriano,
Have you disabled all snapshotting features? Usiong open -r?
How are you starting fossil, what's your configuration?

--
John Soros


On Tuesday 20 April 2010 12:45:09 Adriano Verardo wrote:
> Hi all.
>
> I'm building an industrial  application  hosted by several independent
> cpu server,
> each of them booted from a CFlash on sdD0.
>
> The application doesn't write on sdD0 and there are no redirection on
> local files
> in the cpurc scripts.
>
> In this particular situation fossil should be actually used read only so
> allowing
> to use write protected CF and/or to suddenly power off the system without
> damaging the file system.
>
> Instead, fossil writes on sdD0 (doesn't boot fom a write protected CF)
> and the
> power loss destroy the file system more than fifty-fifty.
>
> Unfortunately I cannot guarantee stable/correct operating conditions.
>
> Any suggestion ?
>
> Thanks in advance
>
> adriano