Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Feb 2012 11:29:53 -0600
From:      Ryan Frederick <ryanrfrederick@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: Kernel Panic on 9.0-RELEASE When Attempting to Remove Files
Message-ID:  <4F355411.6040304@gmail.com>
In-Reply-To: <4F35493A.8040705@gmail.com>
References:  <4F35493A.8040705@gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
In response to the related thread started by Martin McCormick we did run 
a `zpool scrub` on the zpool, and the scrub completed successfully with 
no repairs performed.

I successfully tried importing the zpool in Linux using the native Linux 
ZFS module. However attempting to remove the files via Linux results in 
`rm` either being killed or hanging.

Ryan

On 02/10/2012 10:43 AM, Ryan Frederick wrote:
> I'm attempting to remove a number of old files within a directory that
> was rsynced over from another box. However a number of files (old
> symlinks and regular files in this instance) cause a kernel panic when
> attempting to remove them using rm or unlink.
>
> This is the panic message output:
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 1; apic id = 01
> fault virtual address = 0x160
> fault code = supervisor read data, page not present
> instruction pointer = 0x20:0xffffffff81476306
> stack pointer = 0x28:0xffffff811aacf880
> frame pointer = 0x28:0xffffff811aacf940
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 4729 (rm)
> trap number = 12
> panic: page fault
> cpuid = 1
> KDB: stack backtrace:
> #0 0xffffffff808680fe at kdb_backtrace+0x5e
> #1 0xffffffff80832cb7 at panic+0x187
> #2 0xffffffff80b18400 at trap_fatal+0x290
> #3 0xffffffff80b18749 at trap_pfault+0x1f9
> #4 0xffffffff80b18c0f at trap+0x3df
> #5 0xffffffff80b0313f at calltrap+0x8
> #6 0xffffffff80b7d694 at VOP_REMOVE_APV+0x34
> #7 0xffffffff808cb4fd at kern_unlinkat+0x32d
> #8 0xffffffff80b17cf0 at amd64_syscall+0x450
> #9 0xffffffff80b03427 at Xfast_syscall+0xf7
>
>
>
>
>
> And this is the backtrace from kgdb:
>
> #0 doadump (textdump=Variable "textdump" is not available.
> ) at pcpu.h:224
> #1 0xffffffff808327f5 in kern_reboot (howto=260) at
> /usr/src/sys/kern/kern_shutdown.c:442
> #2 0xffffffff80832ca1 in panic (fmt=Variable "fmt" is not available.
> ) at /usr/src/sys/kern/kern_shutdown.c:607
> #3 0xffffffff80b18400 in trap_fatal (frame=0xc, eva=Variable "eva" is
> not available.
> ) at /usr/src/sys/amd64/amd64/trap.c:819
> #4 0xffffffff80b18749 in trap_pfault (frame=0xffffff811aacf7d0,
> usermode=0) at /usr/src/sys/amd64/amd64/trap.c:735
> #5 0xffffffff80b18c0f in trap (frame=0xffffff811aacf7d0) at
> /usr/src/sys/amd64/amd64/trap.c:474
> #6 0xffffffff80b0313f in calltrap () at
> /usr/src/sys/amd64/amd64/exception.S:228
> #7 0xffffffff81476306 in zfs_freebsd_remove (ap=Variable "ap" is not
> available.
> ) at
> /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1842
>
> #8 0xffffffff80b7d694 in VOP_REMOVE_APV (vop=Variable "vop" is not
> available.
> ) at vnode_if.c:1333
> #9 0xffffffff808cb4fd in kern_unlinkat (td=0xfffffe00046cb8c0,
> fd=-100, path=0x7fffffffdd73 <Address 0x7fffffffdd73 out of bounds>,
> pathseg=UIO_USERSPACE, oldinum=0)
> at vnode_if.h:575
> #10 0xffffffff80b17cf0 in amd64_syscall (td=0xfffffe00046cb8c0,
> traced=0) at subr_syscall.c:131
> #11 0xffffffff80b03427 in Xfast_syscall () at
> /usr/src/sys/amd64/amd64/exception.S:387
> #12 0x00000008009315fc in ?? ()
>
>
>
> This particular system is a VM running on a VMWare ESXi hypervisor. So
> far I haven't had any luck in finding a cause.
>
> Ryan



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4F355411.6040304>