From owner-freebsd-stable@FreeBSD.ORG Wed Jan 8 18:05:56 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 D0D4B812 for ; Wed, 8 Jan 2014 18:05:56 +0000 (UTC) Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8CCD91225 for ; Wed, 8 Jan 2014 18:05:56 +0000 (UTC) Received: by mail-ve0-f177.google.com with SMTP id db12so1535225veb.22 for ; Wed, 08 Jan 2014 10:05:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vuZSrI/phoG/BvEv8CcafXtN08EEPbfgGqQEQ1YQ16U=; b=aPbAXqY1TPX5hhVO9oQhcHyo2+T2R2TG19EpIWZhdyydYD4CoXe326aovH2j4jTwiR opex2H2T1saoFyTJugXCkGpZqbWQGH1Was4vRlYuK9bXTgOY5u4XKeKPk7S9Nc6p+GS3 /Z2UrJN5EbkA7rFtBux3eUGQoeYRpSmfK9QMw4/uvZuf7QB3U52JjcKdUQqrnc2Ae882 OaDlehVipPNGoj9rHdND9DtnAOtrs9X+OPO3dSYMwD8Bj/AkV5PacLr3YdFQKL91dKPm b6umpXFg8I30LoEHX1PSDcquLgj8C0+gHrDmO44ie09m+TcaYSB/Z9r4lXahhsep1enT poPg== MIME-Version: 1.0 X-Received: by 10.58.200.168 with SMTP id jt8mr11254364vec.30.1389204355613; Wed, 08 Jan 2014 10:05:55 -0800 (PST) Received: by 10.58.165.2 with HTTP; Wed, 8 Jan 2014 10:05:55 -0800 (PST) In-Reply-To: References: Date: Wed, 8 Jan 2014 13:05:55 -0500 Message-ID: Subject: Re: UFS panic on Google Compute Engine From: Thomas Hoffmann To: FreeBSD Stable Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Julian Stecklina 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: Wed, 08 Jan 2014 18:05:56 -0000 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 > > Is anyone having the same problem? Unfortunately, it is a bit hard to do > a fsck of / on GCE. I am not sure how I could have destroyed the > filesystem manually while transferring images to GCE. I'll try it a > third time just to be sure... > > Backtrace is: > #0 doadump (textdump=) at pcpu.h:219 > #1 0xffffffff808af570 in kern_reboot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:447 > #2 0xffffffff808af934 in panic (fmt=) > at /usr/src/sys/kern/kern_shutdown.c:754 > #3 0xffffffff80af5668 in ufs_lookup_ino (vdp=0x0, vpp=0xfffffe0033cb39a8, > cnp=0xfffffe0024fe8000, dd_ino=0x0) at > /usr/src/sys/ufs/ufs/ufs_lookup.c:773 > #4 0xffffffff80d97c62 in VOP_CACHEDLOOKUP_APV (vop=, > a=) at vnode_if.c:197 > #5 0xffffffff80937d1f in vfs_cache_lookup (ap=) at > vnode_if.h:80 > #6 0xffffffff80d97b62 in VOP_LOOKUP_APV (vop=, > a=) > at vnode_if.c:129 > #7 0xffffffff8093fefb in lookup (ndp=0xfffffe0033cb3948) at vnode_if.h:54 > #8 0xffffffff8093f684 in namei (ndp=0xfffffe0033cb3948) at > /usr/src/sys/kern/vfs_lookup.c:299 > #9 0xffffffff809531b5 in kern_statat_vnhook (td=0xfffff8001483f000, > flag=, fd=-100, > path=0x7fffffffc400
, > pathseg=UIO_USERSPACE, > sbp=0xfffffe0033cb3a60, hook=) > at /usr/src/sys/kern/vfs_syscalls.c:2270 > #10 0xffffffff8095304d in sys_stat (td=0x0, uap=0xfffffe0033cb3b80) > at /usr/src/sys/kern/vfs_syscalls.c:2250 > #11 0xffffffff80c8efb7 in amd64_syscall (td=0xfffff8001483f000, > traced=0) at subr_syscall.c:134 > #12 0xffffffff80c756ab in Xfast_syscall () at > /usr/src/sys/amd64/amd64/exception.S:391 > > Regards, Julian > > [1] > > https://groups.google.com/forum/#!msg/gce-discussion/YWoa3Aa_49U/FYAg9oiRlLUJ 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.