From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fossil/venti falling down?
Date: Thu, 18 Jun 2009 09:30:08 -0700 [thread overview]
Message-ID: <7d3530220906180930p575fcb4bk473decb7d1a89c27@mail.gmail.com> (raw)
In-Reply-To: <94ba4a9e3deb5a534803ff5821b19c2a@quanstro.net>
On Thu, Jun 18, 2009 at 9:25 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>
> > Forgot to add that I've only seen one error on the console during all of this:
> > /boot/fossil: could not write super block; waiting 10 seconds
> > /boot/fossil: blistAlloc: called on clean block.
>
> is that once, or every time?
>
> - erik
>
It seems to only happen once per boot, but not necessarily when fossil
starts responding--I've seen it a couple hours after booting, which
the filesystem tends to go away at night.
John
--
"I've tried programming Ruby on Rails, following TechCrunch in my RSS
reader, and drinking absinthe. It doesn't work. I'm going back to C,
Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba
next prev parent reply other threads:[~2009-06-18 16:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 16:01 John Floren
2009-06-18 16:21 ` John Floren
2009-06-18 16:25 ` erik quanstrom
2009-06-18 16:30 ` John Floren [this message]
2009-06-18 16:45 ` erik quanstrom
2009-06-18 17:10 ` John Floren
2009-06-24 17:06 ` John Floren
2009-06-21 11:57 ` Richard Miller
2009-06-21 12:12 ` Steve Simon
2009-06-21 14:11 ` erik quanstrom
2009-06-21 19:50 ` Josh Wood
2009-06-24 17:43 ` John Floren
2009-06-24 19:09 ` cinap_lenrek
2009-06-24 23:33 ` John Floren
2009-06-24 23:39 ` erik quanstrom
2009-06-25 0:00 ` Venkatesh Srinivas
2009-06-25 0:42 ` erik quanstrom
2009-06-25 16:13 ` Russ Cox
2009-06-25 16:24 ` erik quanstrom
2009-06-25 16:47 ` Russ Cox
2009-06-25 16:51 ` erik quanstrom
2009-06-25 0:59 ` erik quanstrom
2009-06-25 16:13 ` Russ Cox
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=7d3530220906180930p575fcb4bk473decb7d1a89c27@mail.gmail.com \
--to=slawmaster@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).