Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: F21 fails to mount root part, btrfs check: Couldn't open file system
Date: Tue, 31 Mar 2015 23:45:47 +0200	[thread overview]
Message-ID: <b5hrub-586.ln1@hurikhan77.spdns.de> (raw)
In-Reply-To: CAJCQCtQ9PCv5pNMapQabLBKHOS86B+zavcKsQOiR2Q9qOrxv6g@mail.gmail.com

Chris Murphy <lists@colorremedies.com> schrieb:

> On Tue, Mar 31, 2015 at 2:09 PM, Chris Murphy <lists@colorremedies.com>
> wrote:
> 
>> Well you have to rule that out before anyone on this list can really
>> help. Try booting Fedora 21 install media, and using smartctl -x on
>> the drive.
> 
> While you're at it, try to mount the Btrfs volume in question normally
> and report kernel messages. If mount fails, try it with -o recovery
> mount option, and also report kernel messages and whether that fails.

I had this happen, too, lately. It's quite often happening after an unclean 
shutdown (which currently quite often happend to me due to the xorg intel 
driver having GPU freezes). SysRq+W shows that the mount process is locked 
somewhere in the btrfs code path and won't quit if Ctrl+C'd...

Only way to fix it was to btrfs-zero-log. But it still took some reboots 
from initramfs until it successfully mounted again (I could mount it in 
initramfs right after zero-log but upon reboot it hung again though at a 
different stage probably).

So I guess there's some race on the one hand (happens from time to time non-
related to fixing it with zero-log), and a deadlock on the other hand after 
some unclean shutdowns (more or less random).

My setup is 3-device btrfs-mraid1-draid0 on bcache. Bcache wasn't involved 
in the backtrace of SysRq+W, however. Apparently I don't have a screenshot 
of it because my smart phone is currently fried...

-- 
Replies to list only preferred.


  reply	other threads:[~2015-03-31 21:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 18:55 F21 fails to mount root part, btrfs check: Couldn't open file system Martin Langhoff
2015-03-31 20:09 ` Chris Murphy
2015-03-31 20:11   ` Chris Murphy
2015-03-31 21:45     ` Kai Krakow [this message]
2015-03-31 21:48       ` Kai Krakow
2015-03-31 22:15       ` Chris Murphy
2015-03-31 22:17         ` Chris Murphy
2015-03-31 23:38           ` Kai Krakow
2015-03-31 23:56     ` Martin Langhoff
     [not found]   ` <HK2PR01MB0308B3759FC1AED779C219869AF40@HK2PR01MB0308.apcprd01.prod.exchangelabs.com>
2015-03-31 22:11     ` Chris Murphy
2015-03-31 23:54   ` Martin Langhoff
2015-04-01  1:33     ` Chris Murphy
2015-04-01 15:42       ` Martin Langhoff
2015-04-01 16:15         ` Martin Langhoff
2015-04-01 16:26           ` Martin Langhoff
2015-04-01 17:09           ` Chris Murphy
2015-04-01 17:03         ` Chris Murphy
2015-04-01 17:26           ` Martin Langhoff
2015-04-01 18:04             ` Chris Murphy
2015-04-01 18:16               ` Martin Langhoff
2015-04-01 18:20                 ` Chris Murphy
2015-04-01 18:29                   ` Martin Langhoff
2015-04-01 18:54                     ` Chris Murphy
2015-04-01 19:23                       ` Martin Langhoff
2015-04-01 20:14                         ` Chris Murphy
2015-04-01 20:21                           ` Chris Murphy
2015-04-02  3:29                             ` Chris Murphy
2015-04-01 15:47   ` Martin Langhoff

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=b5hrub-586.ln1@hurikhan77.spdns.de \
    --to=hurikhan77@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox