From owner-freebsd-current@FreeBSD.ORG  Tue Sep  2 05:17:03 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6277C16A4BF
	for <current@freebsd.org>; Tue,  2 Sep 2003 05:17:03 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2F5D543FAF
	for <current@freebsd.org>; Tue,  2 Sep 2003 05:17:02 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id WAA06234;
	Tue, 2 Sep 2003 22:16:41 +1000
Date: Tue, 2 Sep 2003 22:16:40 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: w@dream.vg
In-Reply-To: <20030902085343.GF6853@student.agh.edu.pl>
Message-ID: <20030902220945.V1393@gamplex.bde.org>
References: <20030902085343.GF6853@student.agh.edu.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: Syncer "giving up" on buffers
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Sep 2003 12:17:03 -0000

On Tue, 2 Sep 2003, Jan Srzednicki wrote:

> On Mon, Sep 01, 2003 at 07:53:48PM +0300, Lefteris Chatzibarbas wrote:

> > I have a problem with kernels,  built the last couple of days, where
> > during shutdown syncer is "giving up" on buffers.  During the next boot
> > all filesystems are checked because of improper dismount.  Here follow
> > the exact messages I get:
> > ...
> > After some testing I found out that this does _not_ happen if I manually
> > unmount my ext2 filesystems, before shutting down.  In this case syncer
> > finishes without any problems.
>
> I confirm that, same thing happened in my case. But, I had just one
> buffer remaining and ext2fs mounted in read-only. It seems that it's not
> so read-only then..

Even read-only ext2fs hangs onto the buffers.  They are never dirty in
the read-only case, but they are busy so the code that waits for all
buffers to become non-dirty doesn't even look at them to decide if they
are dirty (it waits for them to become non-busy).  So even clean but
busy buffers prevent a clean shutdown.

Bruce