From owner-freebsd-stable@FreeBSD.ORG Thu Jan 9 02:48:23 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 431B2BA2 for ; Thu, 9 Jan 2014 02:48:23 +0000 (UTC) Received: from os.inf.tu-dresden.de (os.inf.tu-dresden.de [IPv6:2002:8d4c:3001:48::99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 054941D54 for ; Thu, 9 Jan 2014 02:48:23 +0000 (UTC) Received: from [178.0.255.90] (helo=[192.168.178.35]) by os.inf.tu-dresden.de with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) id 1W15fO-0006jl-Vz; Thu, 09 Jan 2014 03:48:19 +0100 Message-ID: <1389235686.3057.4.camel@janus.xn--pl-wia.net> Subject: Re: UFS panic on Google Compute Engine From: Julian Stecklina To: kpneal@pobox.com Date: Thu, 09 Jan 2014 03:48:06 +0100 In-Reply-To: <20140108193938.GA19267@neutralgood.org> References: <20140108193938.GA19267@neutralgood.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.3 (3.10.3-1.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: Thomas Hoffmann , FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2014 02:48:23 -0000 On Mi, 2014-01-08 at 14:39 -0500, kpneal@pobox.com wrote: > On Wed, Jan 08, 2014 at 01:05:55PM -0500, Thomas Hoffmann wrote: > > On Wed, Jan 8, 2014 at 9:40 AM, Julian Stecklina < > > jsteckli@os.inf.tu-dresden.de> wrote: > > > > > Hello, > > > > > > I have set up a FreeBSD 10.0 RC4 system on GCE using this [1] > > > description. I have hit the following panic on two different setups when > > > trying to do portsnap fetch extract and using portinstall: > > > > > > panic: ufs_dirbad: /: bad dir ino 24563 at offset 0: mangled entry > > > I experienced that exact same panic back on 9.1-RELEASE. Every time I > > executed a command that used /var, my system would panic. I cleared it by > > running fsck -y on all filesystems while in single user mode, so that is > > the first thing I would try in spite of the fact that (unfortunately) > > running fsck on GCE is a "bit hard". Sorry. > > The easiest thing to do might be to hack /etc/rc.d/fsck to do the > 'fsck -y' unconditionally. Change the '-p' to '-y' in /etc/rc.d/fsck > and then reboot. After the problem is solved be sure to change it > back to the way it was. Thanks for the tip. Too easy. ;) The filesystem is seriously damaged: Starting file system checks: /dev/da0p2: INCORRECT BLOCK COUNT I=164645 (8 should be 0) (CORRECTED) /dev/da0p2: INCORRECT BLOCK COUNT I=164650 (8 should be 0) (CORRECTED) /dev/da0p2: INCORRECT BLOCK COUNT I=164654 (8 should be 0) (CORRECTED) /dev/da0p2: INCORRECT BLOCK COUNT I=164659 (8 should be 0) (CORRECTED) [... lots of those ...] /dev/da0p2: UNALLOCATED I=4378 OWNER=root MODE=0 /dev/da0p2: SIZE=0 MTIME=Jan 1 00:00 1970 /dev/da0p2: NAME=/usr/ports/math/lapack/files /dev/da0p2: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. Automatic file system check failed; help! I checked the local copy of the image I uploaded to GCE and its filesystem is fine. Must be happened during transfer to GCE. Weird. Sorry for the noise, Julian