9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Anthony Sorace" <anothy@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] More venti sync woes.
Date: Wed, 26 Sep 2007 15:32:32 -0400	[thread overview]
Message-ID: <509071940709261232t1046ecv2ce6800d549c180c@mail.gmail.com> (raw)

I've had a cpu server running off a non-venti-backed fossil for a few
weeks now. the same machine has also been running venti (but the
fossil wasn't talking to it, intentionally). I'd confirmed the venti
was working by doing direct dumps and mounting the results from vacfs.
All was well.

Yesterday I modified my fossil config to use the venti. Edited the
config with fossil/conf, rebooted, and all was well. At boot time, the
"sync..." message stayed for about 10 seconds (I didn't time it, but
that's the right order), as it had been on every previous reboot
(before fossil was using it), and then it moved on and booted as
normal.

Last night something outside my house got struck by lightning and we
lost power for a few seconds. On boot, it hung at the "sync..."
message. It's now been double-digit hours. The disk is slowish, and
lacks supported DMA, but that still seems ridiculous, especially on a
system with now one day's worth of dumps (with less than 50MB data
beyond the stock plan9 install).

On the up side, my microwave, which has been broken for months, is now
working properly again. Go figure.

So I've got questions. First, I was under the impression that venti's
structure made it more or less immune to abrupt shutdown. In that
case, assuming no damage to the actual hardware, is it safe to factor
the power outage out of the equation and just treat this as a reboot?

And the big one: what's going on? I've had this sync issue in a couple
different setups. In the earlier ones, I wrote it off to having
re-used oventi partitions and that confusing nventi. But this has been
all nventi throughout. A handful of folks on IRC have observed
indefinite stalls at the same place. Aside from the clock time theory
proposed just a little bit ago (which is not the case for me; I
checked), I've not heard any good working theories.

My next step is going to be to try booting off some other medium and
rebuild the index partitions, assuming the actual arenas are unharmed.
Any bets on whether that's likely to pay off?

Anthony


             reply	other threads:[~2007-09-26 19:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 19:32 Anthony Sorace [this message]
2007-09-26 19:39 ` Steve Simon
2007-09-26 19:41   ` erik quanstrom
2007-09-26 19:49     ` Anthony Sorace
2007-09-27 21:53 ` Russ Cox
2007-09-27 22:49   ` Anthony Sorace
2007-09-27 23:03     ` erik quanstrom
2007-09-28  3:16     ` Russ Cox
2007-09-28  9:01       ` Kernel Panic
2007-09-28 16:35         ` Anthony Sorace
2007-09-27 23:54   ` Charles Forsyth
2007-09-28  0:10     ` erik quanstrom
2007-09-28  0:19       ` Charles Forsyth
2007-09-28  0:19         ` erik quanstrom
2007-09-28  4:01       ` Bruce Ellis

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=509071940709261232t1046ecv2ce6800d549c180c@mail.gmail.com \
    --to=anothy@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).