HEADS-UP: system deadlock issues when rebooting after updating or upgrading to 10.1-RELEASE

Glen Barber gjb at FreeBSD.org
Thu Mar 12 05:18:21 UTC 2015


It has become apparent that issues reported in PR 195458 [1] do not
apply to freebsd-update(8) users alone, and that the deadlock on reboot
(either via reboot(8) or shutdown(8) with the '-r' flag) can be reliably
reproduced under certain conditions.

Specifically, the issue can be reliably reproduced on systems using UFS
as the root filesystem with soft-updates and journaling enabled (a.k.a.,
SU+J).

Systems using ZFS or UFS without SU+J appear to be unaffected at this
point (noted by various people in the referenced PR, as well as my own
tests).  Based on the comments in the referenced PR, it is unclear if
this deadlock can occur under other conditions, but it seems to be
contained to UFS with SU+J.  If you have experienced a deadlock after
upgrading a 10.1-RELEASE system, please update the referenced PR with
pertinent information (filesystem, and filesystem options, etc.).  While
the underlying cause, and more importantly, a resolution is being
investigated, it is critical we have as much information as possible.

Once the underlying issue is identified, and we have a tested fix for
the problem, an EN will be issued as soon as reasonably possible.

To be clear, this issue manifests as an unresponsive system after
issuing a reboot(8) (or in some cases, a shutdown(8)) command, after the
"All buffers synced." message is displayed, and this heads-up is
addressing only those cases (or potential cases).  All other filesystem
related should be reported in a separate PR, as usual.

Having said all of the above, I as the RE for 10.1-RELEASE, personally
apologize to everyone that has run into this issue.  I am still baffled
why I did not run into this problem when testing 10.1-RELEASE (or any of
the -BETA or -RC builds).  I can only attribute this to a change in my
testing environment (i.e., updated hypervisor software), but given the
details and reproducibility after recent testing, am unable to explain
how this was not discovered earlier.

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195458

Glen
On behalf of:	re@

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20150312/58e763d1/attachment.sig>


More information about the freebsd-stable mailing list