I had at some point used mdconfig to mount an HD image (with the image on an SMB partition) with an msdos partition on it to /dev/md0. I came back a few days later, noticed the disk was still showing as mounted in df, but when I saw the directory was empty, I figured I must have detached the disk without unmounting first. (though while trying to reproduce the bug, this may not have been the case) I did "umount /mnt/dos" first, getting "umount of /mnt/dos failed: Bad file descriptor", and followed that up with "umount -f /mnt/dos", after which my system immediately rebooted. Here is the output from /var/log/messages: Apr 12 20:27:35 goosebox kernel: g_vfs_done():md0s1[READ(offset=512, length=4096)]error = 9 Apr 12 20:27:37 goosebox sudo: hadley : TTY=ttyp1 ; PWD=/mnt ; USER=root ; COMMAND=/sbin/umount dos Apr 12 20:27:37 goosebox kernel: g_vfs_done():md0s1[READ(offset=512, length=4096)]error = 9 Apr 12 20:27:38 goosebox sudo: hadley : TTY=ttyp1 ; PWD=/mnt ; USER=root ; COMMAND=/sbin/umount -f dos Apr 12 20:28:47 goosebox syslogd: kernel boot file is /boot/kernel/kernel How-To-Repeat: Not quite sure... I know at the very least it involves creating a memory disk based off a disk image mounted over the network. It seems that maybe leaving the image mounted for a while and probably rebooting the machine the image is on at some point inbetween caused the disk image to no longer be locatable, causing the reboot when I unmounted it.
Responsible Changed From-To: freebsd-amd64->freebsd-fs Reclassify and reassign.
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped
Keyword: crash – in lieu of summary line prefix: [panic] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>