panic: spin lock held too long (RELENG_8 from today)
hrs at FreeBSD.org
Wed Sep 7 00:48:32 UTC 2011
Attilio Rao <attilio at freebsd.org> wrote
in <CAJ-FndAChGndC=LkZNi7i6mOt+Spw3-OftO9rH0+5WNnVWzuBw at mail.gmail.com>:
at> This should be enough for someone NFS-aware to look into it.
at> Were you also able to get a core?
Yes. But as kib@ pointed out it seems a deadlock in ZFS. Some
experiments I did showed that this deadlock can be triggered at least
by doing "rm -rf" against a local directory that has a large number
Then, I updated the kernel with the latest 8-STABLE + WITNESS option
because a fix for LOR of spa_config lock was committed and tracking
locks without WITNESS was hard. The deadlock can still be triggered
During this investigation an disk has to be replaced and resilvering
it is now in progress. A deadlock and a forced reboot after that
make recovering of the zfs datasets take a long time (for committing
logs, I think), so I will try to reproduce the deadlock and get a
core dump after it finished.
If the old kernel and core of the deadlock I reported on Saturday are
still useful for debugging, I can put them to somewhere you can
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20110907/52693dcb/attachment.pgp
More information about the freebsd-stable