Affected here on a fresh precise server install using lvm. Nice timing Andreas on creating this bug :)
My interpretation of the Debian bug is that they put that workaround in their own package but were seeking a proper fix upstream (probably in the kernel).
Strange thing is that I built a very similar server a couple of weeks ago and I haven't noticed this issue. Wondering whether that might reflect a difference in startup order/timing, or... ??
Affected here on a fresh precise server install using lvm. Nice timing Andreas on creating this bug :)
My interpretation of the Debian bug is that they put that workaround in their own package but were seeking a proper fix upstream (probably in the kernel).
Strange thing is that I built a very similar server a couple of weeks ago and I haven't noticed this issue. Wondering whether that might reflect a difference in startup order/timing, or... ??