From nobody@FreeBSD.org  Fri Jan  5 04:46:18 2001
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id CB37C37B400
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  5 Jan 2001 04:46:17 -0800 (PST)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f05CkH714763;
	Fri, 5 Jan 2001 04:46:17 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200101051246.f05CkH714763@freefall.freebsd.org>
Date: Fri, 5 Jan 2001 04:46:17 -0800 (PST)
From: chris@interface-business.de
Sender: nobody@FreeBSD.org
To: freebsd-gnats-submit@FreeBSD.org
Subject: syncing on shutdown leaves filesystem dirty
X-Send-Pr-Version: www-1.0

>Number:         24085
>Category:       kern
>Synopsis:       syncing on shutdown leaves filesystem dirty
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    remko
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 05 04:50:03 PST 2001
>Closed-Date:    Sat Jan 27 19:00:43 GMT 2007
>Last-Modified:  Sat Jan 27 19:00:43 GMT 2007
>Originator:     Christian Schade
>Release:        4.2-STABLE
>Organization:
Interface Business GmbH
>Environment:
FreeBSD chuck.cube.sax.de 4.2-STABLE FreeBSD 4.2-STABLE #0: Wed Jan  3 21:08:03 CET 2001     root@chuck.cube.sax.de:/usr/obj/usr/src/sys/CHUCK  i386
>Description:
If you have softupdates enabled and write a large file, it's possible
when you shutdown the machine, that syncing gives up before all buffers
are written:

syncing ... 15 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up
>How-To-Repeat:
Write a large file and reboot imediately.
This error may not occur if your harddisk is fast enough
>Fix:
- replace the 20 iterations in syncing by a sysctl variable
- find a better algorithm for syncing

>Release-Note:
>Audit-Trail:

From: Ken Lui <klui@cup.hp.com>
To: freebsd-gnats-submit@FreeBSD.org, chris@interface-business.de
Cc:  
Subject: Re: kern/24085: syncing on shutdown leaves filesystem dirty
Date: Sun, 29 Apr 2001 23:42:30 -0700

 Christian Schade wrote:
 > My workaround is still to have a "sync" and "sleep 30" in /etc/rc.shutdown.
 
 Hmm, I tried it by placing sync and sleep 30 at the end of rc.shutdown,
 and it doesn't solve my A7V's shutdown problem. I get something like 10
 5 1 1 1 1 1 1...for its full 20 iterations. The sleep 30 is working
 because I don't get the syncing disks message later on, but the sync
 command activates my disk for a brief period of time.
 
 I noticed I'm experiencing this problem quite often--7 out of 10
 reboots/shutdowns--after I've added a TDK 12/10/32 ATAPI CDRW to my system.
 
 Primary IDE            - Seagate as Master, Maxtor as secondary
 Secondary IDE          - Pioneer DVD as Master, TDK CDRW as secondary
 
 Promise primary IDE    - none
 Promise secondary IDE  - none
 
 
 Ken

From: "Jose M. Alcaide" <jose@we.lc.ehu.es>
To: freebsd-gnats-submit@FreeBSD.org, chris@interface-business.de
Cc:  
Subject: Re: kern/24085: syncing on shutdown leaves filesystem dirty
Date: Mon, 30 Apr 2001 11:03:22 +0200

 Hmm... Maybe this problem could be related to the disk's write cache.
 Some disks delay the writes to media indefinitely.
 
 Suggestion: upgrade to 4.3-RELEASE or 4-STABLE (WC is now disabled
 by default and there are tunables for enabling it) and see if the
 problem persists.
 
 -- JMA
 ****** Jose M. Alcaide  //  jose@we.lc.ehu.es  //  jmas@FreeBSD.org ******
 ** "Beware of Programmers who carry screwdrivers" --  Leonard Brandwein **

From: Ken Lui <klui@cup.hp.com>
To: freebsd-gnats-submit@FreeBSD.org
Cc: chris@interface-business.de, jose@we.lc.ehu.es
Subject: Re: kern/24085: syncing on shutdown leaves filesystem dirty
Date: Tue, 22 May 2001 08:35:16 -0700

 I've tried using FreeBSD 4.3-STABLE and the problem still persists. 
 sysctl says that hw.ata.wc is 0.
 
 
 Ken
 

From: Ken Lui <klui@cup.hp.com>
To: freebsd-gnats-submit@FreeBSD.org, chris@interface-business.de
Cc:  
Subject: Re: kern/24085: syncing on shutdown leaves filesystem dirty
Date: Mon, 09 Jul 2001 11:00:47 -0700

 I have found that rather than doing a "shutdown -p 0" or "reboot" from 
 multiuser mode, but instead if I bring the box to single-user mode via 
 "shutdown now" then followed by a "reboot"/"shutdown -p 0", then the problem 
 goes away or isn't as prone to not sync properly.
 
 
 Ken
 
State-Changed-From-To: open->feedback 
State-Changed-By: iedowse 
State-Changed-When: Sun Nov 18 11:53:05 PST 2001 
State-Changed-Why:  

Does this problem still occur? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24085 

From: Ian Dowse <iedowse@maths.tcd.ie>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: kern/24085: syncing on shutdown leaves filesystem dirty 
Date: Mon, 19 Nov 2001 14:44:50 +0000

 Adding to the audit trail.
 
 In message <20011119153902.A80069@cube.sax.de>, Christian Schade writes:
 >iedowse@FreeBSD.org (iedowse@FreeBSD.org) wrote:
 >> Synopsis: syncing on shutdown leaves filesystem dirty
 >> 
 >> State-Changed-From-To: open->feedback
 >> State-Changed-By: iedowse
 >> State-Changed-When: Sun Nov 18 11:53:05 PST 2001
 >> State-Changed-Why: 
 >> 
 >> Does this problem still occur?
 >> 
 >> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24085
 >
 >Yes, the problem still occurs. :(
 >
 >Meanwhile I'm using 4.4-stable, but last week the filesytem was dirty
 >after reboot. I modified my /etc/rc.shutdown to wait 30 seconds after
 >doing a sync to give the system enought time to write open files back.
 >It seem to reduce the problem, but last week it didn't help.
 >I have a 40GB disk and it takes about 5 minutes to fsck. :(
 >
 >Sincerly,
 >Christian Schade
State-Changed-From-To: feedback->open 
State-Changed-By: ceri 
State-Changed-When: Sun Jun 8 10:57:11 PDT 2003 
State-Changed-Why:  
Feedback has been requested and received; throw this PR back open. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=24085 
State-Changed-From-To: open->feedback 
State-Changed-By: remko 
State-Changed-When: Sat Dec 30 15:57:55 UTC 2006 
State-Changed-Why:  
hello, is this problem still relevant for recent 
freebsd versions like 6.x? 


Responsible-Changed-From-To: freebsd-bugs->remko 
Responsible-Changed-By: remko 
Responsible-Changed-When: Sat Dec 30 15:57:55 UTC 2006 
Responsible-Changed-Why:  
grab the pr. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=24085 
State-Changed-From-To: feedback->closed 
State-Changed-By: remko 
State-Changed-When: Sat Jan 27 19:00:35 UTC 2007 
State-Changed-Why:  
feedback timeout 

http://www.freebsd.org/cgi/query-pr.cgi?pr=24085 
>Unformatted:
