From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4BCD8C0E.7080003@maht0x0r.net>
Date: Tue, 20 Apr 2010 12:12:14 +0100
From: maht <maht-9fans@maht0x0r.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: 9fans@9fans.net
References: <4BCD85B5.1060404@tecmav.com>
In-Reply-To: <4BCD85B5.1060404@tecmav.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Fossil robustness
Topicbox-Message-UUID: 09c3cb74-ead6-11e9-9d60-3106f5b1d025

On 20/04/2010 11:45, 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
>
Fossil is essentially a cache for Venti, the non-Venti special case is
what you are attempting to use.

Perhaps kfs / cws would be a better choice.

Or even booting from a CD.