From owner-freebsd-current  Thu Nov  9 10:41:55 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id KAA00227
          for current-outgoing; Thu, 9 Nov 1995 10:41:55 -0800
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA00219
          for <current@FreeBSD.org>; Thu, 9 Nov 1995 10:41:50 -0800
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA29380; Thu, 9 Nov 1995 11:37:01 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199511091837.LAA29380@phaeton.artisoft.com>
Subject: Re: Filesystem becomes unstable in -current :-(
To: ache@astral.msk.su (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=)
Date: Thu, 9 Nov 1995 11:37:01 -0700 (MST)
Cc: current@FreeBSD.org
In-Reply-To: <KH-PTemeE4@ache.dialup.demos.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Nov 9, 95 01:22:54 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 414       
Sender: owner-current@FreeBSD.org
Precedence: bulk

> I saw one panic in disksort() and dead process hang on
> "getblk" channel, I never got them before -current...

Are you using the async stuff?

Are you mounting read only, but attempting a write?

I think either of these might result in your problem, given recent patches.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.