From owner-freebsd-bugs  Mon Sep 13  3: 0: 5 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 1F63514F68
	for <freebsd-bugs@FreeBSD.org>; Mon, 13 Sep 1999 03:00:03 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id DAA47761;
	Mon, 13 Sep 1999 03:00:03 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Date: Mon, 13 Sep 1999 03:00:03 -0700 (PDT)
Message-Id: <199909131000.DAA47761@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Bruce Evans <bde@zeta.org.au>
Subject: Re: alpha/13709: panic: sched_sync: fsync failed
Reply-To: Bruce Evans <bde@zeta.org.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR kern/13709; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: Doug Rabson <dfr@nlsystems.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: alpha/13709: panic: sched_sync: fsync failed
Date: Mon, 13 Sep 1999 15:23:07 +1000 (EST)

 >  I think this is a problem with softupdates.
 
 Any write error probably causes this problem.  ffs_fsync() now aborts
 after a write error.  This is just one of the problems caused by
 improving the handling of write errors.
 
 Bruce
 
 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message