From owner-freebsd-current@FreeBSD.ORG  Mon Jun 28 13:54:45 2004
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 7345816A4CE
	for <freebsd-current@FreeBSD.org>;
	Mon, 28 Jun 2004 13:54:45 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F017F43D1D
	for <freebsd-current@FreeBSD.org>;
	Mon, 28 Jun 2004 13:54:44 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i5SDsJkm067510;
	Mon, 28 Jun 2004 06:54:23 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200406281354.i5SDsJkm067510@gw.catspoiler.org>
Date: Mon, 28 Jun 2004 06:54:19 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: kalev@colleduc.ee
In-Reply-To: <40DFBC86.3070103@colleduc.ee>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-current@FreeBSD.org
Subject: Re: Giving up on x buffers - losing files
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: Mon, 28 Jun 2004 13:54:45 -0000

On 28 Jun, Kalev Lember wrote:
> Arjan van Leeuwen wrote:
> 
>> <snip>
>>
>> Sometimes, particularly after doing a lot of file writes (i.e. 
>> compiling a  lot of ports, building world and mergemastering, etc), I 
>> get the 'Giving  up on x buffers' message on shutdown, and my 
>> filesystems come up dirty  when I restart.
>>
>> <snip>
>>
>> So, why does this happen? And how do I prevent it from happening? 
>> This  definitely does _not_ sound like something I want my servers to 
>> do when  5.x goes -STABLE.
> 
> Not sure if it is related, but if I have ext2 mounted on shutdown, the 
> syncer also fails and gives up on a few buffers. It is reproducable. I 
> can recall it was fixed about a year ago, but then broke again.

This is an unrelated bug that has also been discussed.  I believe it
even affects read-only mounts of ext2 file systems.