From owner-freebsd-fs@freebsd.org Tue Apr 5 21:00:53 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8FD6B04533 for ; Tue, 5 Apr 2016 21:00:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 B0C3B1D16 for ; Tue, 5 Apr 2016 21:00:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u35L0rbp049630 for ; Tue, 5 Apr 2016 21:00:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Date: Tue, 05 Apr 2016 21:00:53 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: michelle@sorbs.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 21:00:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207667 --- Comment #2 from Michelle Sullivan --- I hate to be beligerent, but exactly how would one do that... take a phone = into the DC and take a photo of the console? What would be nice would be to know how to get it to dump core... I see no reason why it shouldn't...=20=20 in /etc/rc.conf: # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev=3D"AUTO" Then in /etc/rc.conf.local: dumpdev=3D"AUTO" dumpdir=3D"/var/crash" crashinfo_enable=3D"YES" And just to make sure... # ls -l /var/crash/ total 4 -rw-r--r-- 1 root wheel 5 Sep 27 2013 minfree [root@colossus ~]# more /var/crash/minfree=20 2048 [root@colossus ~]# df -h Filesystem Size Used Avail Capacity Mounted on /dev/mirror/roots1a 107G 50G 48G 51% / devfs 1.0k 1.0k 0B 100% /dev VirtualDisks 69G 31k 69G 0% /VirtualDisks sorbs 33T 29T 3.8T 89% /sorbs [root@colossus ~]# more /etc/fstab=20 # Device Mountpoint FStype Options Dump Pas= s# /dev/mirror/roots1a / ufs rw 1 1 /dev/da0s1 none swap sw 1 0 Even did this: [root@colossus ~]# dumpon -v /dev/da0s1=20 kernel dumps on /dev/da0s1=20 (da0s1 =3D 28G(ish) USB drive - 16G RAM in the machine) ... Oh well photograph the console seems to be the answer ... if it helps: http://flashback.sorbs.net/packages/zpool-scrub-panic-console.jpg --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=