From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fossil errors
Date: Wed, 21 Mar 2007 11:59:01 -0400 [thread overview]
Message-ID: <1efd3e96278a7f66f6aad74867866f19@coraid.com> (raw)
In-Reply-To: <9ab217670703210853g2b268bc6w1bfde7b6538af507@mail.gmail.com>
fossil should never do this. this is a thread locking bug.
btw, why not use "all=+; disk/mkfs -vd $dst -s $src /env/all"?
- erik
On Wed Mar 21 11:54:29 EDT 2007, devon.odell@gmail.com wrote:
> 2007/3/21, erik quanstrom <quanstro@coraid.com>:
> > it means that lock() (/sys/src/9/port/taslock.c:/^lock) is looping way too much
> > in rendezvous. 0x37a34 is in rendezvous.s.
> >
> > i don't know fossil or venti very well. it would be hard to say what is wrong with
> > the threading here without some serious groveling. my wild guess would be that
> > there are three processes (21 26 23) at the same rendezvous point at the same time.
> > rendezvous works for two processes.
> >
> > i wonder why libventi doesn't use the thread library?
>
> In either case, it doesn't seem to happen very often. I got it by @{
> cd ; tar -c . } | tar -xv ing my MP3s. So far, using cpdir, I haven't
> seen any of this yet.
>
> --dho
prev parent reply other threads:[~2007-03-21 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 13:29 Devon H. O'Dell
2007-03-21 15:47 ` erik quanstrom
2007-03-21 15:53 ` Devon H. O'Dell
2007-03-21 15:59 ` erik quanstrom [this message]
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=1efd3e96278a7f66f6aad74867866f19@coraid.com \
--to=quanstro@coraid.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).