To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-bugbusters
or, via email, send a message with subject or body 'help' to
freebsd-bugbu...@freebsd.org
You can reach the person managing the list at
freebsd-bugb...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-bugbusters digest..."
Today's Topics:
1. I was unable to report a zfs bug, incorrect confirmation code
(Christian Nygaard)
----------------------------------------------------------------------
Message: 1
Date: Thu, 26 Nov 2009 15:21:42 +0100
From: Christian Nygaard <christia...@gmail.com>
Subject: I was unable to report a zfs bug, incorrect confirmation code
To: bugbu...@FreeBSD.org
Message-ID:
<4d4321660911260621k115...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Your Electronic Mail Address:
christia...@gmail.com
Your Name:
Christian Nygaard
One line summary of the problem:
zfs removing a zfs storage file causes kernel panic
category:
amd64
Which FreeBSD Release You Are Using:
8.0
Environment (output of "uname -a" on the problem machine):
FreeBSD freebsd 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009
�������������� ro...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC� amd64
Full Description:
Creating a zfs test pool on file based, then removing one of the
underlying files
and doing a zpool scrub causes kernel panic.
How to repeat the problem:
To reproduce create two files, then zpool tank pool on files
# dd if=test1 count=100k bs=1k
# dd if=test2 count=100k bs=1k
# zpool create tank mirror /root/test1 /root/test2
now remove file /root/test2, this causes a kernel panic
# rm /root/test2
# zpool scrub tank
Kernel Panic
��� Fatal trap 12: page fault while in kernel mode
��������� cpuid = 1; apic id = 01
��������� fault virtual address�� = 0x0
��������� fault code������������� = supervisor read data, page not present
��������� instruction pointer���� = 0x20:0xffffffff810735bd
��������� stack pointer���������� = 0x28:0xffffff803e778800
��������� frame pointer���������� = 0x28:0xffffff803e7788c0
��������� 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�������� = 36 (txg_thread_enter)
��������� trap number������������ = 12
��������� panic: page fault
��������� cpuid = 1
��������� Uptime: 3m31s
��������� Cannot dump. Device not defined or unavailable.
��������� Automatic reboot in 15 seconds - press a key on the console to abort
------------------------------
End of freebsd-bugbusters Digest, Vol 218, Issue 2
**************************************************