From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0505141103804ba7c@mail.gmail.com>
Date: Sat, 14 May 2005 14:03:02 -0400
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
In-Reply-To: <32a656c2050514101155984a58@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <775b8d190505101428367bf34e@mail.gmail.com>
	<56b14b2f88d235622337c5374aaaca01@plan9.ucalgary.ca>
	<32a656c205051017331a03d59f@mail.gmail.com>
	<ee9e417a050513092653888bde@mail.gmail.com>
	<ca7c4b96ac0a7fc6925a4ab34af47573@ar.aichi-u.ac.jp>
	<32a656c2050514101155984a58@mail.gmail.com>
Cc: 
Topicbox-Message-UUID: 4bdaf6e6-ead0-11e9-9d60-3106f5b1d025

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. =20

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