Date: Tue, 05 Apr 2016 21:00:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Message-ID: <bug-207667-6-bMpNEkWnAg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-207667-6@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207667 --- Comment #2 from Michelle Sullivan <michelle@sorbs.net> --- 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... in /etc/rc.conf: # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="AUTO" Then in /etc/rc.conf.local: dumpdev="AUTO" dumpdir="/var/crash" crashinfo_enable="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 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 # Device Mountpoint FStype Options Dump Pass# /dev/mirror/roots1a / ufs rw 1 1 /dev/da0s1 none swap sw 1 0 Even did this: [root@colossus ~]# dumpon -v /dev/da0s1 kernel dumps on /dev/da0s1 (da0s1 = 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 -- You are receiving this mail because: You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-207667-6-bMpNEkWnAg>