From owner-freebsd-hackers Sat Sep 20 14:13:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA27375 for hackers-outgoing; Sat, 20 Sep 1997 14:13:47 -0700 (PDT) Received: from usr07.primenet.com (tlambert@usr07.primenet.com [206.165.6.207]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA27369 for ; Sat, 20 Sep 1997 14:13:45 -0700 (PDT) Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA24268; Sat, 20 Sep 1997 14:13:42 -0700 (MST) From: Terry Lambert Message-Id: <199709202113.OAA24268@usr07.primenet.com> Subject: Re: free inode //612 had 208 blocks To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 20 Sep 1997 21:13:41 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970920191957.VJ14474@uriah.heep.sax.de> from "J Wunsch" at Sep 20, 97 07:19:57 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Sep 5 18:10:11 sax /kernel: free inode //612 had 208 blocks > > Is this something to worry about? (Machine running FreeBSD 2.1.) Is this after a crash and reboot? Or an NFS server? If an inode that is being used as a swap store is deleted, then the inode hangs around with a non-zero reference count. When the process goes way, the inode is deleted and the blocks recovered. If this wasn't a fsck message (doesn't look like one), then my guess is that it's over-ambitious error reporting. If it happens frequently, it may be more serious corruption. But a one-time-occurance is not a problem, especially fater one of the two events described above. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.