[Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool...

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Apr 5 21:00:53 UTC 2016


--- Comment #2 from Michelle Sullivan <michelle at 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

Then in /etc/rc.conf.local:


And just to make sure...

# ls -l /var/crash/
total 4
-rw-r--r--  1 root  wheel  5 Sep 27  2013 minfree
[root at colossus ~]# more /var/crash/minfree 
[root at 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 at 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 at 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:


You are receiving this mail because:
You are on the CC list for the bug.

More information about the freebsd-amd64 mailing list