From owner-freebsd-questions@FreeBSD.ORG Wed Jul 9 05:13:42 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C5AD10657B5 for ; Wed, 9 Jul 2008 05:13:42 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (oldagora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 33A418FC32 for ; Wed, 9 Jul 2008 05:13:41 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id m695DNu3074119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 Jul 2008 22:13:23 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id m695DNMf074118; Tue, 8 Jul 2008 22:13:23 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA25107; Tue, 8 Jul 08 22:07:58 PDT Date: Tue, 08 Jul 2008 22:09:38 -0700 From: perryh@pluto.rain.com To: freebsd@edvax.de Message-Id: <48744812.rPIv7fZj6F/Uf5C8%perryh@pluto.rain.com> References: <20080709041051.bad001ab.freebsd@edvax.de> In-Reply-To: <20080709041051.bad001ab.freebsd@edvax.de> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Data loss after power out - fsck: bad inode number to nextinode X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 05:13:47 -0000 > What should I do? In theory, clri {special-file} 306176 should wipe the inode containing the bad pointer and allow fsck to continue, perhaps recovering the files pointed to by that directory into lost+found. Definitely try this on a copy first if at all possible.