From owner-freebsd-bugs@FreeBSD.ORG Sun Nov 16 18:55:22 2014 Return-Path: Delivered-To: freebsd-bugs@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 666E6CB0 for ; Sun, 16 Nov 2014 18:55:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DBD3A56 for ; Sun, 16 Nov 2014 18:55:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAGItMMg048189 for ; Sun, 16 Nov 2014 18:55:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195061] Reproducable kernel panic on 10.1-Release when creating a zfs pool Date: Sun, 16 Nov 2014 18:55:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RC2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: robert@indylix.nl X-Bugzilla-Status: Open X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Nov 2014 18:55:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195061 --- Comment #9 from Robert Sevat --- The dump was indeed from a default ufs formatted install. But I've done it on multiple machines that have zfs as rootfs too: robert@summus:~ % zfs get all zroot/tmp NAME PROPERTY VALUE SOURCE zroot/tmp type filesystem - zroot/tmp creation Thu Nov 6 22:38 2014 - zroot/tmp used 128K - zroot/tmp available 225G - zroot/tmp referenced 128K - zroot/tmp compressratio 1.00x - zroot/tmp mounted yes - zroot/tmp quota none default zroot/tmp reservation none default zroot/tmp recordsize 128K default zroot/tmp mountpoint /tmp local zroot/tmp sharenfs off default zroot/tmp checksum on default zroot/tmp compression lz4 inherited from zroot zroot/tmp atime off inherited from zroot zroot/tmp devices on default zroot/tmp exec on local zroot/tmp setuid off local zroot/tmp readonly off default zroot/tmp jailed off default zroot/tmp snapdir hidden default zroot/tmp aclmode discard default zroot/tmp aclinherit restricted default zroot/tmp canmount on default zroot/tmp xattr off temporary zroot/tmp copies 1 default zroot/tmp version 5 - zroot/tmp utf8only off - zroot/tmp normalization none - zroot/tmp casesensitivity sensitive - zroot/tmp vscan off default zroot/tmp nbmand off default zroot/tmp sharesmb off default zroot/tmp refquota none default zroot/tmp refreservation none default zroot/tmp primarycache all default zroot/tmp secondarycache all default zroot/tmp usedbysnapshots 0 - zroot/tmp usedbydataset 128K - zroot/tmp usedbychildren 0 - zroot/tmp usedbyrefreservation 0 - zroot/tmp logbias latency default zroot/tmp dedup off default zroot/tmp mlslabel - zroot/tmp sync standard default zroot/tmp refcompressratio 1.00x - zroot/tmp written 128K - zroot/tmp logicalused 12K - zroot/tmp logicalreferenced 12K - zroot/tmp volmode default default zroot/tmp filesystem_limit none default zroot/tmp snapshot_limit none default zroot/tmp filesystem_count none default zroot/tmp snapshot_count none default zroot/tmp redundant_metadata all default -- You are receiving this mail because: You are the assignee for the bug.