The system hung and never rebooted, however, it was still alive enough to print the "Limiting closed port RST response" while I was actually watching it, about 8 hours after the panic. Unfortunately, since this is a fully-ZFS system, I do not have any crashdumps. I will add another HDD and just use it to store crashdumps if I start to get panics more often. Screenshot of the console with panic: http://dl.dropbox.com/u/5055904/20110503-freebsd-zfs-panic.png Text on the console: vputx: negative ref count 0xfffffe01334da1e0: tag zfs, type VDIR usecount 0, writecount 0, refcount 1 mountedhere 0 flags (VI_OWEINACT) VI_LOCKed lock type zfs: EXCL by thread 0xfffffe006928d8c0 (pid 9317) with exclusive waiters pending panic: vputx: negative ref cnt cpuid = 2 Uptime 23h46m51s Cannot dump. Device not defined or unavailable. Automatic reboot in 15 seconds - press a key on the console to abort Sleeping thread (tid 101270, pid9317) owns a non-sleepable lock panic: sleeping thread cpuid = 2 Limiting closed port RST response from 210 to 200 packets/sec Fix: Unknown Patch attached with submission follows: How-To-Repeat: The system is an HP DL380 G5 with dual Xeon X5460 CPUs, 32GB RAM, and two LSI SAS HBAs with some Intel X25-E SSDs and a shelf full of disks attached. Link to dmesg: http://dl.dropbox.com/u/5055904/20110503-freebsd-zfs-dmesg.txt The system is scheduled in crontab to reboot every 24 hours in an attempt to improve system stability (due to some freezes, not panics), so based on the Uptime that was printed in the panic and the crontab entries, the scripts which I use to create/delete daily ZFS snapshots may have been running at the time of the panic.
Apologies for the dmesg file attachment showing up under "Fix", I see now that the PR submission page mentions that the attachment is meant for patches. Additionally, I didn't make it clear in the "How-To-Repeat" section that I don't really know how to repeat it, I was just trying to provide more details of the environment that the panic was triggered in. :-)
Responsible Changed From-To: freebsd-bugs->freebsd-fs Over to maintainer(s).
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