Just to clarify because the bug was assigned to Neil: I doubt it's a md related issue. The md device is rightfully busy and cannot be stopped. Rather the shutdown/reboot procedure should eventually give up and continue (as it did previously). Btw, just rebooted and the problem is still reproducible.