All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: "Пламен Петров" <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: Wed, 23 Apr 2014 12:15:46 -0700	[thread overview]
Message-ID: <20140423191546.GG26949@merlins.org> (raw)
In-Reply-To: <001401cf5f27$17cae590$4760b0b0$@petrovi.no-ip.info>

On Wed, Apr 23, 2014 at 10:06:12PM +0300, Пламен Петров wrote:
> Just to clarify - I am using a monolithic kernel built from source, and it has all the stuff it needs to support built-in, and then some. And no modules.
> The sources I'm using are the vanilla kernels from Linus and Greg KH downloaded from kernel.org.

Ok.
 
> Check out the attached config I am using - it’s a kernel I'm running on one server and a couple of virtual machines.

That's the working .config.
I suggest you diff that one with the new one you have for 3.14
 
> Until now - copying said config and doing a "make oldconfig" or "make olddefconfig" and compiling-then-booting worked fine.

This should indeed work, this is what I do too.

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.

My guess is that if you diff both you'll likely find what went wrong, but if
not you can post here.

As for the btrfs FS format, it has not changed in a way that new kernels
wouldn't be able to mount an FS from a year ago or more.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

  reply	other threads:[~2014-04-23 19:15 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 [this message]
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
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=20140423191546.GG26949@merlins.org \
    --to=marc@merlins.org \
    --cc=linux-btrfs@vger.kernel.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 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.