[vivid] btrfs deadlock at mount/boot

[Trent Lloyd]

My btrfs filesystem will not mount almost every boot for a few weeks now. The only way I can currently fix this is to network boot into rescue mode to clear the log, would be great to import this into vivid.

It appears to be this issue:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9c4f61f01d269815bb7c37be3ede59c5587747c6
https://btrfs.wiki.kernel.org/index.php/Gotchas

> Stable kernel version 3.19.1+ can cause a deadlock at mount time
> workaround: boot with older kernel, or run btrfs-zero-log to clear the log (beware of the consequences)
> fix: scheduled for 3.19.5, or apply 9c4f61f01d269815bb7c37.
> also affected: 3.14.35+, 3.18.9+

break-fix: 381cf6587f8a8a8e981bc0c1aaaa8859b51dc756 9c4f61f01d269815bb7c37be3ede59c5587747c6

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1445252

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[rektide de la faye (rektide-g)]

Where is this fix available? I've lost three workstations to this (was unaware of the Gotcha's wiki page which suggests workarounds)

[rektide de la faye (rektide-g)]

Re previous: oh, that's Debian where the fix was released. Pardon. Really hoping for a stable/non-self-immolating VV system.

[rektide de la faye (rektide-g)]

Using a 4.0 kernel is a workaround. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Thorsten Hirsch (t-hirsch)]

This problem is being triggered every time I don't shutdown cleanly. Here's my disk layout:

/boot ext4
/ btrfs

One workaround seems to be: booting a CD or USB stick and repairing the root fs.

[h (sairia-b)]

Please add trusty as affected, due to package linux-image-generic-lts-utopic

$ apt-cache policy linux-image-extra-3.16.0-34-generic
linux-image-extra-3.16.0-34-generic:
  Installed: 3.16.0-34.47~14.04.1
  Candidate: 3.16.0-34.47~14.04.1
  Version table:
 *** 3.16.0-34.47~14.04.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages

We have tried serveral times, booting with 3.16.0-33 is ok, 3.16.0.34 fails

[elventear (elventear)]

Has the fix been released for Trusty?

[Julian Taylor (jtaylor)]

it is available via -proposed in version 3.16.0-38.52~14.04.1
https://wiki.ubuntu.com/Testing/EnableProposed

it will move to -updates when its tested

[Rolf Leggewie (r0lf)]

utopic has seen the end of its life and is no longer receiving any updates. Marking the utopic task for this ticket as "Won't Fix".

[Andy Whitcroft (apw)]

This bug was nominated against a series that is no longer supported, ie vivid. The bug task representing the vivid nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.