From: Russ Cox <russcox@gmail.com>
To: Vester Thacker <vester.thacker@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 server controls impaired and steps taken before
Date: Sat, 14 May 2005 14:03:02 -0400 [thread overview]
Message-ID: <ee9e417a0505141103804ba7c@mail.gmail.com> (raw)
In-Reply-To: <32a656c2050514101155984a58@mail.gmail.com>
I'd be frustrated too. I've never seen a wait that long.
I made a bad design choice in the locking of fossil blocks
and I apologize. My suggestion would be to run sync
and then halt at the console, reboot, and let it start
again.
There is a window (I think ten seconds) between snap -a
and fossil deciding to start archiving. If you access any
file in those ten seconds then enough of the root gets
copied-on-write that you shouldn't see the deadlock at all.
Rebooting should cause enough file activity at startup
to get around the deadlock.
Russ
next prev parent reply other threads:[~2005-05-14 18:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 1:43 [9fans] Plan 9 server controls impaired and steps taken before failure Vester Thacker
2005-05-10 1:50 ` andrey mirtchovski
2005-05-10 21:28 ` Bruce Ellis
2005-05-10 23:14 ` [9fans] Plan 9 server controls impaired and steps taken before andrey mirtchovski
2005-05-11 0:33 ` Vester Thacker
2005-05-13 16:26 ` Russ Cox
2005-05-13 21:29 ` arisawa
2005-05-14 17:11 ` Vester Thacker
2005-05-14 18:03 ` Russ Cox [this message]
2005-05-14 22:06 ` arisawa
2005-05-14 22:33 ` Russ Cox
2005-05-16 6:10 YAMANASHI Takeshi
2005-05-16 9:04 ` Richard Miller
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=ee9e417a0505141103804ba7c@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=vester.thacker@gmail.com \
/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).