From owner-freebsd-bugs Sun Jan 11 03:07:35 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA11598 for bugs-outgoing; Sun, 11 Jan 1998 03:07:35 -0800 (PST) (envelope-from owner-freebsd-bugs) Received: from spinner.netplex.com.au (root@spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA11561 for ; Sun, 11 Jan 1998 03:07:26 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id TAA05342; Sun, 11 Jan 1998 19:06:54 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199801111106.TAA05342@spinner.netplex.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "John S. Dyson" cc: freebsd-bugs@hub.FreeBSD.ORG Subject: Re: kern/5467: unlink() leaves unrefed files on file sytem In-reply-to: Your message of "Sun, 11 Jan 1998 01:50:01 PST." <199801110950.BAA06788@hub.freebsd.org> Date: Sun, 11 Jan 1998 19:06:53 +0800 From: Peter Wemm Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "John S. Dyson" wrote: > Christopher T. Johnson said: > > >Number: 5467 > > >Category: kern > > >Synopsis: unlink() leaves unrefed files on file sytem > This is a known problem in current as of the date that you have noted. It i s > better now, but I suggest re-supping and trying again on 13 Jan 98. (I have > fixes in my local tree, and will be committing them tomorrow.) You are not wrong! :-] I just ran into this (and other problems - syscons is screwed at the moment!) a short while ago. I found that if I do a 'reboot', the system will perform heavy disk activity for about three minutes *after* the 'Syncing disks.. done', and apon eventual reboot, the filesystems are clean, all the space has come back etc. 'sync; fsck -n /usr' reported something like a couple of thousand unreferenced files before reboot, and /usr was at 106% full. After the disk activity at reboot, and after booting into single-user and doing a 'mount -r /usr' and a df, the space was back to normal - before any fsck etc. I did a 'pstat -v' before the shutdown and it reported something like 17,000 vnodes with flags 'V', HOLD = 1, USE = 0. I checked a handful of inodes that fsck -n reckoned were unreferenced, and sure enough they were on the list in that state. Cheers, -Peter