From owner-freebsd-bugs@FreeBSD.ORG  Sun Nov 16 20:24:32 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
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 42F79432
 for <freebsd-bugs@FreeBSD.org>; Sun, 16 Nov 2014 20:24:32 +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 2997E37D
 for <freebsd-bugs@FreeBSD.org>; Sun, 16 Nov 2014 20:24:32 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAGKOWPG029990
 for <freebsd-bugs@FreeBSD.org>; Sun, 16 Nov 2014 20:24:32 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 194976] [10.1-RELEASE][panic] ZFS TRIM. Kernel dies within
 seconds after mounting ZFS. vfs.zfs.trim.enabled=0 fixes it
Date: Sun, 16 Nov 2014 20:24:32 +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 Only Me
X-Bugzilla-Who: smh@FreeBSD.org
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: <bug-194976-8-SsgXMKoPgk@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-194976-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-194976-8@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Nov 2014 20:24:32 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194976

--- Comment #3 from Steven Hartland <smh@FreeBSD.org> ---
(In reply to Palle Girgensohn from comment #2)
> File backed volume? No, it uses gpt partitions?
> 
> # zpool history
> History for 'tank':
> 2013-02-25.14:56:06 zpool create -f -o altroot=/mnt -o
> cachefile=/var/tmp/zpool.cache tank /dev/gpt/disk0.nop
> 2013-02-25.14:56:22 zpool export tank
> 2013-02-25.14:58:23 zpool import -o altroot=/mnt -o
> cachefile=/var/tmp/zpool.cache tank
> 2013-02-25.15:00:15 zpool set bootfs=tank tank
> ...
> 
> It is a zfs-on-root setup, probably setup according to the guidelines of
> https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE

Your trace disagrees as it mentions vdev_file_io_start which is only called for
a volume created from a file if it was gpt that would be vdev_geom_io_start.

Can you let us know your pool layout with zdb please.

-- 
You are receiving this mail because:
You are the assignee for the bug.