From owner-freebsd-current Sat Jul 15 23:45:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA07385 for current-outgoing; Sat, 15 Jul 1995 23:45:06 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA07368 for ; Sat, 15 Jul 1995 23:45:00 -0700 Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id XAA13544; Sat, 15 Jul 1995 23:44:24 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id XAA00180; Sat, 15 Jul 1995 23:45:34 -0700 Message-Id: <199507160645.XAA00180@corbin.Root.COM> To: Bruce Evans cc: current@freebsd.org Subject: Re: nfs leaves unreferenced files or blocks In-reply-to: Your message of "Sun, 16 Jul 95 16:09:58 +1000." <199507160609.QAA16321@godzilla.zeta.org.au> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 15 Jul 1995 23:43:32 -0700 Sender: current-owner@freebsd.org Precedence: bulk >For a:/usr nfs-mounted on /usr, the space for files created, written to and >deleted by nfs is not recovered when the files are deleted, or when a:/usr >is unmounted. It is recovered when system `a' is rebooted. > >This is with -current after the nfs speed fix in vfs_bio.c and the buggy >fix in trap.c but before the second fix to trap.c. Nevermind my last message; this only happens if the _server_ is running -current (e.g. it is not a client problem). I am able to reproduce the bug here, but I don't think it is related to any of the recent changes. I think it is related to the NFSv3 stuff. Shouldn't be too difficult to fix. -DG