Date: Mon, 11 Apr 2005 20:53:29 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Don Lewis <truckman@FreeBSD.org> Cc: kris@obsecurity.org Subject: Re: Softupdates not preventing lengthy fsck Message-ID: <20050412035111.GA31366@xor.obsecurity.org> In-Reply-To: <200504120143.j3C1hHv4034269@gw.catspoiler.org> References: <20050411234512.GA23344@xor.obsecurity.org> <200504120143.j3C1hHv4034269@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050412035111.GA31366>