From blank@sliphost37.uni-trier.de  Sat Jul  6 06:52:43 1996
Received: from sliphost37.uni-trier.de (root@sliphost37.uni-trier.de [136.199.240.37])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA25769
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 6 Jul 1996 06:52:39 -0700 (PDT)
Received: (from blank@localhost) by sliphost37.uni-trier.de (8.7.5/8.6.12) id OAA04192; Sat, 6 Jul 1996 14:00:50 +0200 (MET DST)
Message-Id: <199607061200.OAA04192@sliphost37.uni-trier.de>
Date: Sat, 6 Jul 1996 14:00:50 +0200 (MET DST)
From: blank@sliphost37.uni-trier.de
Reply-To: blank@sliphost37.uni-trier.de
To: FreeBSD-gnats-submit@freebsd.org
Subject: kernel doesn't flush all its buffers when told to halt the system
X-Send-Pr-Version: 3.2

>Number:         1371
>Category:       kern
>Synopsis:       kernel doesn't flush all its buffers when told to halt the system
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul  6 07:00:02 PDT 1996
>Closed-Date:    Sat Oct 26 11:05:47 PDT 1996
>Last-Modified:  Sat Oct 26 11:06:14 PDT 1996
>Originator:     Sascha Blank
>Release:        FreeBSD 2.1-STABLE i386
>Organization:
University of Trier, Germany
>Environment:

System: FreeBSD 2.1-STABLE with CTM-Patches up to #136
Architecture: Intel Pentium 133, EIDE harddisc and CD-ROM, no SCSI devices,
48 MByte RAM, Triton Chipset

>Description:

About one out of two attempts to shutdown and halt my system using the
command "shutdown -h now" ends up like this:

syncing disks... 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 giving up

If this happens, then it is always buffer 4 that can't be flushed. As far
as I have noticed the amount of process and/or memory load does not
influence the occurence of this error. I encountered it sometimes right
after shutting down and halting a system that has been rebooted a minute
ago, while at other times halting my machine after running for some days
under some heavier load works correctly.

I am quite sure the error was introduced in one of the CTM patches >=
#120 (I guess it was somewhere around #128, but I am not sure). Before
that crucial patch I have never had any problems halting my machine.

>How-To-Repeat:

Enter "shutdown -h now" and watch, if all buffers are flushed correctly.

>Fix:

No idea yet.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: scrappy 
State-Changed-When: Tue Oct 22 21:28:42 PDT 1996 
State-Changed-Why:  

Confirm Status 
State-Changed-From-To: feedback->closed 
State-Changed-By: scrappy 
State-Changed-When: Sat Oct 26 11:05:47 PDT 1996 
State-Changed-Why:  

Originator confirms closure... 

>Unformatted:
