public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Leszek Ciesielski <skolima@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: "No filesystem could mount root" after adding a second device to fs
Date: Mon, 30 Nov 2009 09:51:11 -0500	[thread overview]
Message-ID: <20091130145111.GB4046@localhost.localdomain> (raw)
In-Reply-To: <23a15590911300341t6d4a73f5qc41fbea063d93cdf@mail.gmail.com>

On Mon, Nov 30, 2009 at 12:41:29PM +0100, Leszek Ciesielski wrote:
> Hi,
> 
> after adding a second device to a btrfs filesystem (kernel 2.6.31)
> used for root fs, I am getting a "No filesystem could mount root"
> message upon reboot. Is the caveat
> 
> "btrfsctl -a is used to scan all of the block devices under /dev and
> probe for Btrfs volumes. This is required after loading the btrfs
> module if you're running with more than one device in a filesystem. "
> 
> still true? If yes, is there a technical reason for it - am I wrong to
> assume that btrfs could execute the scan upon mount request when the
> filesystem requires it for assembling?
> 

The btrfs module needs to have an idea of what devices are available for it to
use.  The btrfsctl -a needs to be done in userspace since it scans /dev for
block devices to probe to see if they are btrfs devices.  To do it in the kernel
would require calling out to userspace to run btrfsctl -a for the uncommon case
that you are booting from a multi-disk setup.  Hopefully as btrfs becomes more
and more common distributions will start putting btrfsctl -a in their initrd's
if they detect you have a mutli-disk root.  Thanks,

Josef

      reply	other threads:[~2009-11-30 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 11:41 "No filesystem could mount root" after adding a second device to fs Leszek Ciesielski
2009-11-30 14:51 ` Josef Bacik [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=20091130145111.GB4046@localhost.localdomain \
    --to=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=skolima@gmail.com \
    /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