All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hendrik Friedel <hendrik@friedels.name>
To: Chris Murphy <lists@colorremedies.com>
Cc: Hugo Mills <hugo@carfax.org.uk>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: booting from BTRFS works only with one device in the pool
Date: Wed, 3 Feb 2016 07:31:06 +0100	[thread overview]
Message-ID: <56B19EAA.4000702@friedels.name> (raw)
In-Reply-To: <CAJCQCtS3fQuypTbwTe4=H95rwtN0dMih_nPaBiWUc2s-qE2Xag@mail.gmail.com>

Hello,
>> I would like to go the sensible way :-)
>> But can you hint me how and where to add the btrfs device scan option to the
>> initramfs?
> If btrfs-progs 4.3.1 is installed already, dracut -f will rebuild the
> initramfs and should just drag in current tools which will include
> 'btrfs device scan'.
>

Yes, 4.3.1 is installed and even in the recovery-mode (i.e. if boot 
fails) btrfs reports version 4.3.1.
Also, in this recovery mode, btrfs dev scan is working. Furthermore, I 
can mount the drive in this recovery mode (which I *suspect* is the 
initramfs).

My understanding is/was, that it is not sufficient that btrfs dev scan 
is available, but also its execution must be triggered.  Is that right?

> Like I said above, just install the distribution's own
> btrfs-progs/btrfs-tools package, and it should do the right thing. You
> may have to tell the distribution to rebuild the initramfs

I have run dracut -f. It does not solve the issue.

 >This is CentOS 7.2 installed to a single VDI file, and then you use
 > 'btrfs dev add' to add another VDI file? I'd like to know how to 
reproduce the conditions
 > so I can figure out what's wrong because it ought to work, seeing as 
it worked for me with
 > Fedora 19 and CentOS 7.x is in the vicinity of Fedora 19/20.

Yes, it is Rockstor (CentOS 7.2  based) installed in the way you mention.

Regards,
Hendrik


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


  reply	other threads:[~2016-02-03  6:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 21:31 booting from BTRFS works only with one device in the pool Hendrik Friedel
2016-02-01 22:11 ` Hugo Mills
2016-02-01 23:02   ` Duncan
2016-02-01 23:15     ` Hugo Mills
2016-02-02 22:01   ` Hendrik Friedel
2016-02-02 22:06     ` Chris Murphy
2016-02-03  6:31       ` Hendrik Friedel [this message]
2016-02-02 22:09     ` Hugo Mills
2016-02-01 23:29 ` Chris Murphy
2016-02-02 21:59   ` Hendrik Friedel
2016-02-02 22:04     ` Chris Murphy
2016-02-03 18:14       ` Hendrik Friedel
2016-02-03 20:30         ` Chris Murphy
2016-02-03 22:19           ` Chris Murphy
2016-02-13 14:38             ` Hendrik Friedel
2016-02-13 18:20               ` Chris Murphy

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=56B19EAA.4000702@friedels.name \
    --to=hendrik@friedels.name \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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 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.