linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: raid0 needs mounting alternate device every boot? open_ctree failed (3.19.5)
Date: Sun, 26 Apr 2015 12:32:04 -0700	[thread overview]
Message-ID: <20150426193204.GA5904@merlins.org> (raw)
In-Reply-To: <20150426153226.GA18187@carfax.org.uk>

On Sun, Apr 26, 2015 at 03:32:26PM +0000, Hugo Mills wrote:
>    The usual reason for this is that btrfs dev scan isn't being run
> properly. It's usually handled by udev -- most distributions will put
> the appropriate hooks in their udev configuration if you have the
> distribution's btrfs-progs package installed. If you have only a
> self-built btrfs-progs from git installed, then the udev hooks
> probably aren't there, and you'll need to configure it yourself (or
> arrange to have btrfs dev scan run after the cryptsetup open
> operation).

Ah, yes, that makes more sense.

I do have package and the rules:
gargamel:~# dpkg -L btrfs-tools 
/.
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/80-btrfs-lvm.rules
/lib/udev/rules.d/70-btrfs.rules

But it's very possible that udev isn't working properly or timely on
this system.

I added "btrfs device scan" to /etc/init.d/cryptdisks

Thanks for the help.
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/                         | PGP 1024R/763BE901

      reply	other threads:[~2015-04-26 19:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26 15:20 raid0 needs mounting alternate device every boot? open_ctree failed (3.19.5) Marc MERLIN
2015-04-26 15:32 ` Hugo Mills
2015-04-26 19:32   ` Marc MERLIN [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=20150426193204.GA5904@merlins.org \
    --to=marc@merlins.org \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).