From nobody@FreeBSD.ORG Sun Sep 12 10:01:36 1999 Return-Path: Received: by hub.freebsd.org (Postfix, from userid 32767) id 2416C1540B; Sun, 12 Sep 1999 10:01:36 -0700 (PDT) Message-Id: <19990912170136.2416C1540B@hub.freebsd.org> Date: Sun, 12 Sep 1999 10:01:36 -0700 (PDT) From: Jan@online.be Sender: nobody@FreeBSD.ORG To: freebsd-gnats-submit@freebsd.org Subject: panic: sched_sync: fsync failed X-Send-Pr-Version: www-1.0 >Number: 13709 >Category: kern >Synopsis: panic: sched_sync: fsync failed >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Sep 12 10:10:01 PDT 1999 >Closed-Date: Thu May 30 21:56:34 PDT 2002 >Last-Modified: Thu May 30 21:56:34 PDT 2002 >Originator: Jan >Release: 3.2 RELEASE >Organization: Online Internet >Environment: 3.2-RELEASE FreeBSD 3.2-RELEASE #53: Fri Sep 3 14:37:45 CEST 1999 digital Workstation 433a 512Mb Ram >Description: "panic: sched_sync: fsync failed" shows up at dmesg resulting in a reboot >How-To-Repeat: dunno, the machine does a lot of i/o & network traffic about 3.5Mbit/sec in & out. ( Newsfeeder Box - Diablo ) >Fix: >Release-Note: >Audit-Trail: Responsible-Changed-From-To: freebsd-alpha->freebsd-bugs Responsible-Changed-By: peter Responsible-Changed-When: Sun Sep 12 11:28:47 PDT 1999 Responsible-Changed-Why: This is not an alpha specific bug, it just happened on an PII here. (but running postfix, not diablo) From: Doug Rabson To: Jan@online.be Cc: freebsd-gnats-submit@freebsd.org Subject: Re: alpha/13709: panic: sched_sync: fsync failed Date: Sun, 12 Sep 1999 19:32:14 +0100 (BST) I think this is a problem with softupdates. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 From: Bruce Evans To: Doug Rabson 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 State-Changed-From-To: open->feedback State-Changed-By: iedowse State-Changed-When: Mon Jan 21 13:19:01 PST 2002 State-Changed-Why: Do these panics still occur on more recent releases? http://www.FreeBSD.org/cgi/query-pr.cgi?pr=13709 State-Changed-From-To: feedback->closed State-Changed-By: silby State-Changed-When: Thu May 30 21:56:11 PDT 2002 State-Changed-Why: This PR has been in feedback for 4 months now, and regards FreeBSD 3.2. Time to close it. http://www.freebsd.org/cgi/query-pr.cgi?pr=13709 >Unformatted: