From owner-freebsd-current@FreeBSD.ORG  Tue Apr 12 03:53:31 2005
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 9653616A4CE; Tue, 12 Apr 2005 03:53:31 +0000 (GMT)
Received: from obsecurity.dyndns.org
	(CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 53A2B43D46; Tue, 12 Apr 2005 03:53:31 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id 0B93F51326; Mon, 11 Apr 2005 20:53:29 -0700 (PDT)
Date: Mon, 11 Apr 2005 20:53:29 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: Don Lewis <truckman@FreeBSD.org>
Message-ID: <20050412035111.GA31366@xor.obsecurity.org>
References: <20050411234512.GA23344@xor.obsecurity.org>
	<200504120143.j3C1hHv4034269@gw.catspoiler.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <200504120143.j3C1hHv4034269@gw.catspoiler.org>
User-Agent: Mutt/1.4.2.1i
cc: current@FreeBSD.org
cc: kris@obsecurity.org
Subject: Re: Softupdates not preventing lengthy fsck
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, 12 Apr 2005 03:53:31 -0000

On Mon, Apr 11, 2005 at 06:43:17PM -0700, Don Lewis wrote:
> On 11 Apr, Kris Kennaway wrote:
> > I'm seeing the following problem: on 6.0 machines which have had a lot
> > of FS activity in the past but are currently quiet, an unclean reboot
> > will require an hour or more of fscking and will end up clearing
> > thousands of inodes:
> >=20
> > [...]
> > /dev/da0s1e: UNREF FILE I=3D269731  OWNER=3Droot MODE=3D100644
> > /dev/da0s1e: SIZE=3D8555 MTIME=3DApr 18 02:29 2002  (CLEARED)
>=20
> > /dev/da0s1e: UNREF FILE I=3D269741  OWNER=3Droot MODE=3D100644
> > [...]
> >=20
> > It's as if dirty buffers aren't being written out properly, or
> > something.  Has anyone else seen this?
>=20
> This looks a lot like it could be a vnode refcnt leak.  Files won't get
> removed from the disk while they are still in use (the old unlink while
> open trick).  Could nullfs be a factor?

Yes, I make extensive use of read-only nullfs.

Kris (fsck still running)