Date: Wed, 8 Jan 2014 13:05:55 -0500 From: Thomas Hoffmann <trh411@gmail.com> To: FreeBSD Stable <freebsd-stable@freebsd.org> Cc: Julian Stecklina <jsteckli@os.inf.tu-dresden.de> Subject: Re: UFS panic on Google Compute Engine Message-ID: <CAB7-odkZAGxgtfnqNwNaCfqXcY0nmbFPdf3NtFYkwGUictJcyw@mail.gmail.com> In-Reply-To: <lajo13$2g6$1@ger.gmane.org> References: <lajo13$2g6$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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=<value optimized out>) 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=<value optimized out>) > 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=<value optimized out>, > a=<value optimized out>) at vnode_if.c:197 > #5 0xffffffff80937d1f in vfs_cache_lookup (ap=<value optimized out>) at > vnode_if.h:80 > #6 0xffffffff80d97b62 in VOP_LOOKUP_APV (vop=<value optimized out>, > a=<value optimized out>) > 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=<value optimized out>, fd=-100, > path=0x7fffffffc400 <Address 0x7fffffffc400 out of bounds>, > pathseg=UIO_USERSPACE, > sbp=0xfffffe0033cb3a60, hook=<value optimized out>) > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB7-odkZAGxgtfnqNwNaCfqXcY0nmbFPdf3NtFYkwGUictJcyw>