RE: Can anyone boot a system using btrfs root with linux 3.14 or newer?

From: "Пламен Петров" <plamen@petrovi.no-ip.info>
To: "'Marc MERLIN'" <marc@merlins.org>
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 20:44:06 +0300	[thread overview]
Message-ID: <000a01cf5fe4$ca59aad0$5f0d0070$@petrovi.no-ip.info> (raw)
In-Reply-To: <20140424173317.GI7884@merlins.org>

> -----Original Message-----
> From: Marc MERLIN [mailto:marc@merlins.org]
> Sent: Thursday, April 24, 2014 8:33 PM
> To: Пламен Петров
> Cc: linux-btrfs@vger.kernel.org
> Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or
> newer?
> 
> On Thu, Apr 24, 2014 at 08:19:21PM +0300, Пламен Петров wrote:
> > I just realized that the l gave no way for identifying the particular bugzilla
> entry. Here it is:
> > https://bugzilla.kernel.org/show_bug.cgi?id=74261
> 
> Thanks.
> 
> But to save us a lot more speculation, can you please try booting a linux
> system (either initrd, or another one with a non btrfs root), and then trying
> to mount that filesystem from the command line?

Using 3.14.1 perhaps?

I will try to do that now, but if I can't manage to do it today - expect the results tomorrow.

One more detail I managed to rule out today is that my problematic filesystems used subvol-other-than-root as default, made like so:

$ mount /dev/sda2 /sda2 -o relatime,compress=zlib,subvol=system-main-fs 
$ btrfs subvolume set-default system-main-fs /sda2

Only using different name for the subvolume.
Anyway - its irrelevant.
I formatted a fresh root as BTRFS, skipped the above, and tried booting 3.14.1 - result was kernel panic. So different default subvolume or not - its not the problem.
---------------------------------
Plamen Petrov