From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 15:14:48 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34199F0C for ; Mon, 9 Feb 2015 15:14:48 +0000 (UTC) Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B331EEBA for ; Mon, 9 Feb 2015 15:14:47 +0000 (UTC) X-AuditID: 1209190f-f793f6d000006ae0-c7-54d8cdb1aa94 Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 82.98.27360.1BDC8D45; Mon, 9 Feb 2015 10:09:37 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id t19F9bgE011810; Mon, 9 Feb 2015 10:09:37 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t19F9Y41025417 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 9 Feb 2015 10:09:36 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id t19F9YHk022147; Mon, 9 Feb 2015 10:09:34 -0500 (EST) Date: Mon, 9 Feb 2015 10:09:33 -0500 (EST) From: Benjamin Kaduk To: Willem Jan Withagen Subject: Re: Panic during fsck in bhyve VM In-Reply-To: <54D89A69.1000206@digiware.nl> Message-ID: References: <54D89A69.1000206@digiware.nl> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOIsWRmVeSWpSXmKPExsUixG6norvx7I0Qg0VLbCyOPf7JZvF06jxm ByaPd2dvMnnM+DSfJYApissmJTUnsyy1SN8ugSvj8TTrgkViFRN21DYwtgh1MXJwSAiYSCy5 Y9nFyAlkiklcuLeerYuRi0NIYDGTxItLm5lAEkICGxglbtxjhLAPMkn8fcMFYddLXJy9GCzO IqAlseXOAmYQm01ARWLmm41sILaIgKbEht6bzCC7mAWkJO6srQAJCwOVr+t8zwJicwpoS5z9 uQpsFa+Ag8SUhzOh1mpJ/Hr4AswWFdCRWL1/CgtEjaDEyZlPwGxmoJrl07exTGAUnIUkNQtJ agEj0ypG2ZTcKt3cxMyc4tRk3eLkxLy81CJdE73czBK91JTSTYyg8OSU5N/B+O2g0iFGAQ5G JR7eC5+vhwixJpYVV+YeYpTkYFIS5Y04fSNEiC8pP6UyI7E4I76oNCe1+BCjBAezkgiv6VKg HG9KYmVValE+TEqag0VJnHfTD74QIYH0xJLU7NTUgtQimKwMB4eSBG/FGaBGwaLU9NSKtMyc EoQ0EwcnyHAeoOENIDW8xQWJucWZ6RD5U4yKUuK8CSAJAZBERmkeXC8sfbxiFAd6RZj3EUgV DzD1wHW/AhrMBDS4oABscEkiQkqqgXFORvUsSdFyl2+FuRt2Gx0QeDklaaX35d3vVu2pvvPU +9Bu/Tu1Yh/vds5YzW+yrEPOnj9XouKNfk96vYpIzQS92S75LE0P2fgCW+bVWl/603pa1a1/ mt4jf5NFM08dFpf5edZIdNmRVsaO/d+V2yuSvFYw/j9hvueLC4Otf/axwm+Pd6rsC1NiKc5I NNRiLipOBAC8RUov+gIAAA== Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 15:14:48 -0000 On Mon, 9 Feb 2015, Willem Jan Withagen wrote: > Hi, > > Probably due to too many hard-resets of the VM, but I've got the root fs of > one of my VMs in a real bad state..... > Even where recovery with fsck does not lead to the wanted result. > > Recovering might be interesting, but not essential since it is just a testing > image. > > The traceback is below. I've saved the image, en getting it online is real > easy. > > If this helps in getting UFS/fsck bugs fixed, I'll keep it. > Otherwise it is going into /dev/null > > --WjW > > > WARNING: WITNESS option enabled, expect reduced performance. > Trying to mount root from ufs:/dev/vtbd0p2 [rw]... > WARNING: / was not properly dismounted > Enter full pathname of shell or RETURN for /bin/sh: > # fsck / > ** /dev/vtbd0p2 > > USE JOURNAL? [yn] y > > ** SU+J Recovering /dev/vtbd0p2 > ** Reading 33554432 byte journal from inode 4. > > RECOVER? [yn] y > > ** Building recovery table. > ** Resolving unreferenced inode list. > ** Processing journal entries. > > ***** FILE SYSTEM MARKED CLEAN ***** > # df > Filesystem 512-blocks Used Avail Capacity Mounted on > /dev/vtbd0p2 30450552 15277136 12737376 55% / > devfs 2 2 0 100% /dev > # mount -rw / > panic: ufs_dirbad: /: bad dir ino 1364363 at offset 512: mangled entry This does not seem consistent with the subject line of the email. The first thing to try is to run fsck without using the journal. -Ben Kaduk > cpuid = 1 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe02332b12b0 > vpanic() at vpanic+0x189/frame 0xfffffe02332b1330 > panic() at panic+0x43/frame 0xfffffe02332b1390 > ufs_lookup_ino() at ufs_lookup_ino+0xecd/frame 0xfffffe02332b14b0 > VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0xf1/frame 0xfffffe02332b14e0 > vfs_cache_lookup() at vfs_cache_lookup+0xd6/frame 0xfffffe02332b1540 > VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xf1/frame 0xfffffe02332b1570 > lookup() at lookup+0x5c5/frame 0xfffffe02332b1600 > namei() at namei+0x526/frame 0xfffffe02332b16c0 > vn_open_cred() at vn_open_cred+0xd5/frame 0xfffffe02332b1820 > kern_openat() at kern_openat+0x257/frame 0xfffffe02332b19a0 > amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe02332b1ab0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe02332b1ab0 > --- syscall (499, FreeBSD ELF64, sys_openat), rip = 0x800b09fba, rsp = > 0x7fffffffe868, rbp = 0x7fffffffe940 --- > KDB: enter: panic > [ thread pid 19 tid 100051 ] > Stopped at kdb_enter+0x3e: movq $0,kdb_why > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >