Fails to mount Btrfs

Bug #1442294 reported by Silvio-frischi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Since 3.16.0-34 my computer won't mount my rootfs (btrfs) anymore. 3.16.0-33 still works. I tried it manually with 'break=mount' but it just stops doing anything during the mount command (mount -t btrfs /dev/... /root). kernel panic??? But there is nothing printed on the screen except the three lines that appear anyway.

Btrfs loaded
BTRFS: device fsid 9fc2c5a8-902a-4dd8-8019-10383570e021 devid 1 transid 469974 /dev/mapper/petrocvol-root
BTRFS info (device dm-2): disk space caching is enabled

My btrfs is on an encrypted luks, but that part works fine.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1442294

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-ckt9-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key utopic
tags: added: regression-update
Revision history for this message
Silvio-frischi (silvio-frischi) wrote :

the mainline kernel you linked boots fine. I'm running it right now.
uname -a
Linux petroc 3.16.7-031607-generic #201503300635 SMP Mon Mar 30 10:36:26 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Silvio-frischi (silvio-frischi) wrote :

I can amend that it's not a kernel panic. The mount command just gets stuck in an unkillable state not even kill -9 will kill it. Maybe stuck in some system call. Unfortunately, strace is not in the initramfs. dmesg shows nothing except the three lines I already posted

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue may already be resolved since it does not occur in the latest upstream kernel. Per comment #3, the v3.16.7-ckt9 kernel does not exhibit this bug. The latest Ubuntu kernel in the -proposed repository has all of the v3.16.7-ckt9 updates.

Would it be possible for you to test this latest kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Thank you in advance!

Revision history for this message
Silvio-frischi (silvio-frischi) wrote :

I already had proposed/backports/updates enabled. I can't find a kernel version newer than 3.16.0-34. I'm on Ubuntu 14.10 x86_64.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Actually the 3.16.0-35 kernel has the 3.16.7-ckt9 upstream updates. Can you test the -35 kernel? It can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1442292/

Revision history for this message
Silvio-frischi (silvio-frischi) wrote :

3.16.0-34 suddenly seems to work now. Can't reproduce the bug anymore. Maybe there was some problem installing the package that got fixed when i installed some other kernel.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for the update. I'll mark this bug as incomplete for now. Just change the status back to confirmed if you see the bug again.

Thanks for the help!

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.