9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil/venti falling down?
Date: Sun, 21 Jun 2009 10:11:23 -0400	[thread overview]
Message-ID: <dde22050be348f51eede30e0a8a4b76f@quanstro.net> (raw)
In-Reply-To: <5adefdf7dd429504c13b95bb3dbeab5a@hamnavoe.com>

On Sun Jun 21 07:59:52 EDT 2009, 9fans@hamnavoe.com 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.
>
> I get a few of these nearly every day.  I've been assuming they are benign.

this error sets off alarms for me.  the comment in the
code is "BUG", and naively, i can't work out
a) why the author added that comment,
b) what superWrite would be competing with for
a lock on the superblock (blockWrite returns 0 if
it !vtCanLock from _cacheLocalLookup), and
c) why superWrite isn't doing a vtLock rather than
a vtCanLock, and
d) what happens if b is stll dirty (as per comment)
and a crash occurs.

can someone explain why these are all okay?

- erik



  parent reply	other threads:[~2009-06-21 14:11 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
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 [this message]
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=dde22050be348f51eede30e0a8a4b76f@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).