linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: Alex Elsayed <eternaleye+usenet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Unable to mount btrfs rootfs over after merging bcache
Date: Tue, 7 Aug 2012 02:02:04 -0700	[thread overview]
Message-ID: <CAH+dOx+U4uHQGw2yS7Pr7ObKQ7YVVJoV789+caEOKwpMbh9ZHw@mail.gmail.com> (raw)
In-Reply-To: <jvqffl$6ci$1@dough.gmane.org>

I'll give it a try and see what happens - we'll see if I can reproduce it.

On Tue, Aug 7, 2012 at 12:18 AM, Alex Elsayed
<eternaleye+usenet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi, I've found that if I merge bcache into my kernel it causes booting with
> a btrfs rootfs on top of dm-thin (with dm-crypt under it) to fail. In 3.4 it
> looped indefinitely IIRC, whereas with 3.5 it OOPSed until panic.
>
> I don't have logs, sadly, as this occurs before I have a writable FS.
>
> I will note that I don't have a bcache device, and this occurs even if
> bcache is compiled out.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2012-08-07  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  7:18 Unable to mount btrfs rootfs over after merging bcache Alex Elsayed
2012-08-07  9:02 ` Kent Overstreet [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=CAH+dOx+U4uHQGw2yS7Pr7ObKQ7YVVJoV789+caEOKwpMbh9ZHw@mail.gmail.com \
    --to=koverstreet-hpiqsd4aklfqt0dzr+alfa@public.gmane.org \
    --cc=eternaleye+usenet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).