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: Wed, 24 Jun 2009 10:06:22 -0700 [thread overview]
Message-ID: <7d3530220906241006t7e9799f8r17f09f57c1c41831@mail.gmail.com> (raw)
In-Reply-To: <7d3530220906181010l25557061k774bb250a4a2e6dd@mail.gmail.com>
On Thu, Jun 18, 2009 at 10:10 AM, John Floren<slawmaster@gmail.com> wrote:
> On Thu, Jun 18, 2009 at 9:45 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>>
>> > 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.
>>
>> the failure is somewhere in blockWrite. since blockWrite
>> calls diskWrite and diskWrite just queues up i/o to send
>> to the disk, it's not possible to get i/o errors directly from
>> blockWrite.
>>
>> there are two case that do return errors.
>>
>> one is if the block can't be locked. a runaway periodic function
>> would make that more likely, since we don't wait for the lock.
>> but it seems more likely in this case that some of fossil's data is
>> corrupted since this started after the double-failure.
>> see http://9fans.net/archive/2009/03/487
>>
>> the other case is a funny dependency. there's a fprint there
>> that's commented out.
>>
>> - erik
>>
>
> Here's another message that may be of interest. I ran fshalt before
> rebooting (to test the periodicthread patch) and saw this:
>
> syncing.../srv/fscons...prompt: sourceRoot: fs->ehi = 5395, b->l =
> BtDir,3,Copied,e=5394,-1,tag=0x1
> venti...
> halting.../srv/fscons...archive vac:a9d9b0b9fe0db783fe618f680804a18df532a67a
>
> I don't remember seeing that "sourceRoot: ..." stuff before; as soon
> as the system comes back up I guess I'll take a look at source.
>
After replacing the problematic server and moving the fossil disk to
the new machine, we're not getting random hangs any more.
However, I've seen this a few times on the console:
/boot/fossil: cacheLocalData: addr=78989 type got 0 exp 0: tag got
e63eb942 exp 663eb942
archive(0, 0x1348d): cannot find block: block label mismatch
and
/boot/fossil: cacheLocalData: addr=134772 type got 0 exp 0: tag got
7795335e exp 7715335e
is this something to worry about?
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-24 17:06 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 [this message]
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=7d3530220906241006t7e9799f8r17f09f57c1c41831@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).