From owner-freebsd-questions@FreeBSD.ORG Fri Apr 9 12:51:01 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F1E16A4CE for ; Fri, 9 Apr 2004 12:51:01 -0700 (PDT) Received: from sage.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD74943D1D for ; Fri, 9 Apr 2004 12:51:00 -0700 (PDT) (envelope-from kline@tao.thought.org) Received: from thought.org (tao [10.0.0.247]) by sage.thought.org (8.12.9/8.11.4) with ESMTP id i39JotQ8077072; Fri, 9 Apr 2004 12:50:56 -0700 (PDT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (localhost [127.0.0.1]) by thought.org (8.12.9p2/8.11.3) with ESMTP id i39JorN9043574; Fri, 9 Apr 2004 12:50:53 -0700 (PDT) (envelope-from kline@tao.thought.org) Received: (from kline@localhost) by tao.thought.org (8.12.9p2/8.12.11/Submit) id i39JopG9043573; Fri, 9 Apr 2004 12:50:51 -0700 (PDT) (envelope-from kline) Date: Fri, 9 Apr 2004 12:50:50 -0700 From: Gary Kline To: Ion-Mihai Tetcu Message-ID: <20040409195050.GA43521@tao.thought.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing 17 years of service to the Unix community User-Agent: Mutt/1.5.6i cc: FreeBSD Mailing List Subject: inode problems... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2004 19:51:01 -0000 Just to bring you (and the -questions list) up to date re my 4.9-RELEASE snafu. I did a upgrade last night. I have stable-supfile pointing to RELENG_4_9. I was trying to get back to 4.9-STABLE. No-joy. I now have FreeBSD 4.9-RELEASE-p4 #4: Thu Apr 8 19:50:47 PDT 2004. I don't know if this upgrade made any difference, but I think I fixed my partially alloc'd and otherwise bad inode by hand. find / -inum [inode] -print showed me what was whhere and I dealt with each one. Bottom line is that fsck now runs clean; no errors. I think I'll hack fsck to output a -L logfile in /var/log. I could script it with " |& tee logfile" too. In rare cases like these, having a log of inodes could be a great help. gary -- Gary Kline kline@thought.org www.thought.org Public service Unix