From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: unable to mount a btrfs file system kernel 3.19.2
Date: Mon, 20 Apr 2015 10:49:31 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.04.20.10.49.31@googlemail.com> (raw)
In-Reply-To: 5534D201.7080803@onsd.eu
On Mon, 20 Apr 2015 12:16:33 +0200, Némoz Saint-Dizier, Olivier wrote:
> Hello everyone,
>
> I have an issue with my ssd where a btrfs partition is located. I have a
> /dev/sdb1 in ext4 for the /boot, and the rest of the ssd is /dev/sdb2
> which is the root of my Archlinux. When I boot, it hangs up after
> loading the kernel. So I tried with an Archlinux liveboot, and I have
> the same behavior with the following trace in logs when I try to mount
> the btrfs partition :
[..snip]
> Apr 11 16:25:56 archiso kernel: [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
> Apr 11 16:25:56 archiso kernel: [<ffffffffa043f7ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
> Apr 11 16:25:56 archiso kernel: [<ffffffffa04c3213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
> Apr 11 16:25:56 archiso kernel: [<ffffffff8155e999>] schedule+0x29/0x70
> Is it a known bug? Or does someone have an idea about how I could fix
> this issue?
This hang on mount was caused by a backported fix to -stable, which you
probably caught after an update to 3.19.2.
The fix is in 3.19.5: commit 0187ad2b69a51a23924cd41f730e2d923535db80 in
https://kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.19.5
So just get a fresh 3.19.5 (or directly 4.0) and it should mount again.
-h
prev parent reply other threads:[~2015-04-20 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 10:16 unable to mount a btrfs file system kernel 3.19.2 "Némoz Saint-Dizier, Olivier"
2015-04-20 10:27 ` Hugo Mills
2015-04-20 10:33 ` "Némoz Saint-Dizier, Olivier"
2015-04-20 14:49 ` Is btrfs on top of bcache stable now? Marc MERLIN
2015-04-20 15:34 ` Fábio Pfeifer
2015-04-20 10:49 ` Holger Hoffstätte [this message]
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=pan.2015.04.20.10.49.31@googlemail.com \
--to=holger.hoffstaette@googlemail.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 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.