Bug 133150 - [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while writing data
Summary: [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while writing data
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 7.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-fs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-28 05:30 UTC by osmo.server
Modified: 2010-10-08 10:59 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description osmo.server 2009-03-28 05:30:01 UTC 
After setting up ZFS for the first time, and doing some simple stress tests, I was able to quickly crash my system.

I was able to grab this from the core dump in /var/crash:
ad6: FAILURE - device detached
subdisk6: detached
ad6: detached


Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address   = 0x50
fault code              = supervisor write data, page not present
instruction pointer     = 0x8:0xffffffff80306035
stack pointer           = 0x10:0xffffffffd4d9fbc0
frame pointer           = 0x10:0xffffffffd4d9fc00
code segment            = base rx0, limit 0xfffff, type 0x1b
<118>Mar 27 20:55:39 osmo root: ZFS: vdev failure, zpool=tank type=vdev.open_failed

                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 3 (g_up)
trap number             = 12
panic: page fault
cpuid = 1
Uptime: 3m47s
Physical memory: 4076 MB
Dumping 490 MB:

How-To-Repeat: 
	1. create a raidz zpool with 3 disks
	2. execute:
		 cat /dev/zero > /zpoolname/file &
		 cat /dev/urandom > /zpoolname/file2 &
		 zpool scrub zpoolname
		 zpool iostat 3
	3. let it run for awhile until the system crashes (less than an hour)
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-03-30 01:51:20 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 2 Ivan Voras freebsd_committer freebsd_triage 2009-03-31 13:36:57 UTC 
Can you try to repeat the error on 8-CURRENT?
Comment 3 K. Macy freebsd_committer freebsd_triage 2009-05-17 05:47:42 UTC 
State Changed
From-To: open->feedback



awaiting feedback on ZFS_MFC branch
Comment 4 Jaakko Heinonen freebsd_committer freebsd_triage 2010-10-08 10:59:45 UTC 
State Changed
From-To: feedback->closed

Feedback timeout.