Comment 7 for bug 1568097

Similar mdadm error for me when I resume from suspend on 16.04.2 LTS.

> This bug seems to be fixed in yakkety with mdadm 3.4-4.

Note that while v4.4 was released early 2016, Xenial shipped with v3.3 (which is sane given one wouldn't want to ship with v4.4 just a few mere months after it was released) .

However, what seems a bit tardy to me is that v3.3.4 release was published 03 Aug-2015, so why did/does Xenial ship with a v3.3.2 version and miss two minor releases worth of fixes/updates from upstream (or have to back port them)?

```
$ mdadm --version
mdadm - v3.3 - 3rd September 2013
$ dpkg-query --show mdadm
mdadm 3.3-2ubuntu7.2
```

Of course, there are back-ported patches from v3.4...

https://launchpad.net/ubuntu/+source/mdadm/+changelog