Bug 13709

Summary:	panic: sched_sync: fsync failed
Product:	Base System	Reporter:	Jan <Jan>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description Jan 1999-09-12 18:10:01 UTC

"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 )

Comment 1 Peter Wemm freebsd_committer

1999-09-12 19:28:47 UTC

Responsible Changed
From-To: freebsd-alpha->freebsd-bugs

This is not an alpha specific bug, it just happened on an PII here. 
(but running postfix, not diablo)

Comment 2 Doug Rabson 1999-09-12 19:32:14 UTC

I think this is a problem with softupdates.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037

Comment 3 Bruce Evans 1999-09-13 06:23:07 UTC

>  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

Comment 4 iedowse freebsd_committer

2002-01-21 21:19:01 UTC

State Changed
From-To: open->feedback


Do these panics still occur on more recent releases?

Comment 5 silby freebsd_committer

2002-05-31 05:56:11 UTC

State Changed
From-To: feedback->closed

This PR has been in feedback for 4 months now, and regards 
FreeBSD 3.2.  Time to close it.