9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Adriano Verardo <a.verardo@tecmav.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fossil robustness
Date: Tue, 20 Apr 2010 13:29:29 +0200	[thread overview]
Message-ID: <4BCD9019.1060601@tecmav.com> (raw)
In-Reply-To: <4BCD8C0E.7080003@maht0x0r.net>

maht wrote:
> 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.
I've made a customized install procedure copying from the standard one.
Where can i find
a procedure for kfs to copy from?  Can kfs be configured to be
absolutely insentive to hard power down ?
>
> Or even booting from a CD.
I've only a CF slot. And, in any case, the environment doesn't allow to
use mechanical devices.
>
>
>
>
>
>
>




  reply	other threads:[~2010-04-20 11:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 10:45 Adriano Verardo
2010-04-20 11:12 ` maht
2010-04-20 11:29   ` Adriano Verardo [this message]
2010-04-20 12:32     ` erik quanstrom
2010-04-20 12:50       ` Adriano Verardo
2010-04-21  4:49       ` [9fans] updating 9vx root EBo
2010-04-21  5:18         ` Fernan Bolando
2010-04-21  5:29           ` EBo
2010-04-21  5:45             ` Fernan Bolando
2010-04-21  6:31         ` yy
2010-04-21 11:58           ` EBo
2010-04-21 12:20             ` EBo
2010-04-20 11:13 ` [9fans] Fossil robustness John Soros
2010-04-20 11:39   ` Adriano Verardo
2010-04-20 12:18     ` John Soros
2010-04-20 12:37 ` erik quanstrom
2010-04-20 16:05 ` Anthony Sorace
2010-04-20 17:55   ` [9fans] 9vx crashing EBo
2010-04-20 18:05     ` erik quanstrom
2010-04-20 18:13       ` EBo
2010-04-21  8:39         ` Balwinder S Dheeman
2010-04-21  8:56           ` ron minnich
2010-04-21 11:22           ` erik quanstrom
2010-04-21 12:27             ` Balwinder S Dheeman
2010-04-21 13:05               ` EBo
2010-04-21 13:10                 ` ron minnich
2010-04-21 13:17                   ` EBo
     [not found]                   ` <twig.1271856045.77201@swcp.com>
2010-04-21 13:22                     ` EBo
2010-04-26  4:18           ` lucio
2010-04-26  4:27             ` EBo
2010-04-26  4:30               ` lucio
2010-04-26 10:13                 ` EBo
2010-04-26 12:30                   ` lucio
2010-04-26 15:15             ` Balwinder S Dheeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BCD9019.1060601@tecmav.com \
    --to=a.verardo@tecmav.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).