All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ochi <ochi@arcor.de>
To: rbellamy@pteradigm.com
Cc: linux-btrfs@vger.kernel.org
Subject: Upgrade to 3.19.2 Kernel fails to boot
Date: Sun, 22 Mar 2015 22:15:47 +0100	[thread overview]
Message-ID: <550F3103.7080609@arcor.de> (raw)
In-Reply-To: <CADw2B2Nxr5PPSaVWpQWxg0ZaXYSpOTye_pMU1HbjCHif8q9_LQ@mail.gmail.com>

> When I upgrade to the 3.19.2 Kernel I get a deadlocked boot:
> INFO: task mount:302 blocked for more than 120 seconds.
> INFO: task btrfs-transacti:329 blocked for more than 120 seconds.

I had a similar behavior today after I accidentally pulled the power 
plug of my machine (Arch Linux, Kernel 3.19.2). I tried to boot several 
times, but "mount" timed out. I booted into a recovery Arch Linux with a 
3.18 kernel and my root filesystem mounted without any problems. 
Unmounted, ran btrfs check, no errors. After reboot, the filesystem 
mounted normally with 3.19.2 again! I tried to reproduce this behavior 
on another machine, but so far to no avail.

I'm afraid I wasn't able to gather more debug info. Some more general 
info: I'm using btrfs on top of dm-crypt (LUKS), my root is on a SSD, 
and I'm using rw,noatime,ssd,discard,space_cache as mount options.

  parent reply	other threads:[~2015-03-22 21:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 23:06 Upgrade to 3.19.2 Kernel fails to boot G. Richard Bellamy
2015-03-19 23:19 ` Chris Murphy
2015-03-22 21:15 ` Ochi [this message]
2015-03-22 21:25   ` Roman Mamedov
2015-03-23  8:23 ` Anand Jain
2015-03-23 13:22   ` Rich Freeman
2015-03-23 16:37     ` Rich Freeman
2015-03-24  6:31       ` Anand Jain
2015-03-24 10:40         ` Rich Freeman
2015-04-01  6:50           ` Anand Jain
2015-04-01 19:48             ` Rich Freeman
2015-03-31 21:24 ` Benjamin Hodgetts
2015-03-31 22:23   ` Chris Murphy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=550F3103.7080609@arcor.de \
    --to=ochi@arcor.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rbellamy@pteradigm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.