public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: "Marc MERLIN" <marc@merlins.org>,
	"Пламен Петров" <plamen@petrovi.no-ip.info>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or newer?
Date: Thu, 24 Apr 2014 08:36:24 -0400	[thread overview]
Message-ID: <53590548.5000301@fb.com> (raw)
In-Reply-To: <535904BB.1090307@fb.com>



On 04/24/2014 08:34 AM, Chris Mason wrote:
>
>
> On 04/23/2014 04:58 PM, Marc MERLIN wrote:
>> On Wed, Apr 23, 2014 at 10:37:44PM +0300, Пламен Петров wrote:
>>>> So now, we're kind of guessing. To save us all time, could you
>>>> capture a serial
>>>> console boot from the running 3.13 and then the failing 3.14.
>>>
>>> Well, for the details - see for example here:
>>> https://bugzilla.kernel.org/attachment.cgi?id=133111
>>> how does a 3.14.1 built the way described earlier fails.
>>
>> Thanks, that helps.
>> Except, now I'm perplexed.
>>
>> It indeed shows btrfs loaded and your block device being detected.
>> However it does not show a btrfs mount error.
>
> The mount error is popping up after the printk about not being able to
> find root.  Add rootwait to the command line.

Sorry, that's almost but not quite what I meant to say.  The device 
detection message is popping up after the printk about not being able to 
find root.  Add rootwait to the command line.

In other words, the mount is failing before the root device is detected. 
  rootwait will make us wait (forever) instead of failing.

-chris


  reply	other threads:[~2014-04-24 12:35 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 17:30 Can anyone boot a system using btrfs root with linux 3.14 or newer? Пламен Петров
2014-04-23 18:33 ` Swâmi Petaramesh
2014-04-23 18:54 ` Marc MERLIN
2014-04-23 19:02   ` Hugo Mills
2014-04-23 19:06   ` Пламен Петров
2014-04-23 19:15     ` Marc MERLIN
2014-04-23 19:37       ` Пламен Петров
2014-04-23 20:58         ` Marc MERLIN
2014-04-23 21:54           ` Пламен Петров
2014-04-23 22:03             ` Marc MERLIN
2014-04-23 22:20               ` Пламен Петров
2014-04-23 22:40                 ` Chris Murphy
2014-04-23 22:43                   ` Hugo Mills
2014-04-23 22:50                     ` Marc MERLIN
2014-04-23 22:53                       ` Hugo Mills
2014-04-23 22:41               ` Hugo Mills
2014-04-24 12:34           ` Chris Mason
2014-04-24 12:36             ` Chris Mason [this message]
2014-04-24 17:08               ` Пламен Петров
2014-04-24 17:19       ` Пламен Петров
2014-04-24 17:33         ` Marc MERLIN
2014-04-24 17:44           ` Пламен Петров
2014-04-24 18:51           ` Пламен Петров
2014-04-24 19:31             ` Marc MERLIN
2014-04-24 20:26               ` Пламен Петров
2014-04-24 21:47                 ` Chris Murphy
2014-04-24 21:06             ` Chris Murphy
2014-04-24 21:23               ` Пламен Петров
     [not found]               ` <000c01cf600b$b01f6cf0$105e46d0$@petrovi.no-ip.info>
2014-04-24 23:07                 ` Marc MERLIN
2014-04-25  0:04                   ` Chris Murphy
2014-04-25  0:08                     ` Chris Mason
2014-04-25  5:04                       ` Пламен Петров
2014-04-25  7:02                       ` Duncan
2014-04-25  5:03                     ` Пламен Петров
2014-04-23 19:06 ` Kai Krakow
2014-04-23 20:25   ` Calvin Walton
2014-04-23 22:34   ` Chris Murphy
2014-04-24  3:23 ` Chris Murphy
2014-04-24  6:27   ` Fajar A. Nugraha

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=53590548.5000301@fb.com \
    --to=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.org \
    --cc=plamen@petrovi.no-ip.info \
    /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