From owner-freebsd-stable  Sat May 11 04:45:48 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id EAA07848
          for stable-outgoing; Sat, 11 May 1996 04:45:48 -0700 (PDT)
Received: from asstdc.scgt.oz.au (asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA07839
          for <stable@freebsd.org>; Sat, 11 May 1996 04:45:42 -0700 (PDT)
Received: (from imb@localhost)
          by asstdc.scgt.oz.au (8.7.5/BSD4.4) id VAA07323
          for stable@freebsd.org; Sat, 11 May 1996 21:45:09 +1000 (EST)
From: michael butler <imb@scgt.oz.au>
Message-Id: <199605111145.VAA07323@asstdc.scgt.oz.au>
Subject: guaranteed panic on -stable :-(
To: stable@freebsd.org
Date: Sat, 11 May 1996 21:45:07 +1000 (EST)
X-Mailer: ELM [version 2.4 PL24beta]
Content-Type: text
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I found out the hard way this evening how to guarantee that a -stable
machine can be made to panic .. simply mount a file-system 'async', tar it
up, unmount it, newfs with more inodes, mount it and untar the contents back.

I found this in the process of rearranging a news-spool .. there must be
some sort of race-condition in the kernel associated with 'async'. Without
it, everything is fine but many times slower :-(

	michael