Date: Wed, 12 Nov 2014 23:16:44 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194976] New: [10.1-RELEASE][panic] ZFS TRIM. Kernel dies within seconds after mounting ZFS. vfs.zfs.trim.enabled=0 fixes it Message-ID: <bug-194976-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194976 Bug ID: 194976 Summary: [10.1-RELEASE][panic] ZFS TRIM. Kernel dies within seconds after mounting ZFS. vfs.zfs.trim.enabled=0 fixes it Product: Base System Version: 10.1-RC2 Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: girgen@FreeBSD.org Hi, booted in single user mode. /etc/rc.d/zfs start two seconds... then... boom: KDB: stack backtrace: #0 0xffffffff8096eec0 at kdb_backtrace+0x60 #1 0xffffffff80933b95 at panic+0x155 #2 0xffffffff80d66c1f at trap_fatal+0x38f #3 0xffffffff80d66f38 at trap_pfault+0x308 #4 0xffffffff80d6659a at trap+0x47a #5 0xffffffff80d4c482 at calltrap+0x8 #6 0xffffffff819e8a9c at dmu_write_uio_dnode+0xcc #7 0xffffffff819e89ab at dmu_write_uio_dbuf+0x3b #8 0xffffffff81a7a5b2 at zfs_freebsd_write+0x5e2 #9 0xffffffff80e85c35 at VOP_WRITE_APV+0x145 #10 0xffffffff809e37e9 at vn_rdwr+0x299 #11 0xffffffff81a36e55 at vdev_file_io_start+0x165 #12 0xffffffff81a54676 at zio_vdev_io_start+0x326 #13 0xffffffff81a51382 at zio_execute+0x162 #14 0xffffffff81a84e9e at trim_map_commit+0x2ae #15 0xffffffff81a84ce7 at trim_map_commit+0xf7 #16 0xffffffff81a84ce7 at trim_map_commit+0xf7 #17 0xffffffff81a84a32 at trim_thread+0xf2 Uptime: 1m28s I added vfs.zfs.trim.enabled=0 to /boot/loader.conf and it boots nicely. It is an HP DL360 with ciss0: <HP Smart Array P410i>. Just a single volume presented to the OS, so it is not JBOD, and there are no SSD disks involved. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194976-8>