From: John Soros <sorosj@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fossil robustness
Date: Tue, 20 Apr 2010 14:18:33 +0200 [thread overview]
Message-ID: <201004201418.36176.sorosj@gmail.com> (raw)
In-Reply-To: <4BCD928F.4030702@tecmav.com>
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
next prev parent reply other threads:[~2010-04-20 12:18 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
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 [this message]
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=201004201418.36176.sorosj@gmail.com \
--to=sorosj@gmail.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).