From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID5 doesn't mount on boot, but you can afterwards?
Date: Sun, 4 Oct 2015 02:28:29 +0000 (UTC) [thread overview]
Message-ID: <pan$3b7e2$ac9e4b37$ac602701$c91b77c@cox.net> (raw)
In-Reply-To: 003401d0fe1d$999b41a0$ccd1c4e0$@gmx.de
guido_kuenne posted on Sat, 03 Oct 2015 22:53:46 +0200 as excerpted:
> Beginner here, so just if it helps: My two-device raid 1 mounts on boot
> in Fedora 22 (uuid in fstab, no further devices specified) but I mount
> the fs via uuid while Sjoerd mounted subvolumes. From what I understand
> (not much) it's either an subvolume issue or Fedora must then somehow
> perform a device scan before handling fstab.
I'm guessing fedora has btrfs device scan in its initr*.
I believe dracut is a fedora based project and what they use to generate
their initr*s. I too use dracut for my initr* generation, and btrfs is
an optional module which I obviously load (in a site-specific custom
initr* here, on gentoo), and I know it has the btrfs device scan in the
initr* here, so presumably it's in the general purpose initr* they use as
well. The only way it wouldn't would be if they didn't include the btrfs
dracut module at all in their initr*, and I think btrfs is popular enough
that they include it, so...
... So even if Fedora doesn't include btrfs device scan in the real-root
init (which I'd guess it does as well), it's going to be in the initr*,
which means unless the devices for that btrfs aren't plugged in until
after boot, it should see them due to the scan at the initr* stage, and
"just work", mounting the btrfs without problems at any time after that.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-10-04 2:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 16:49 RAID5 doesn't mount on boot, but you can afterwards? Sjoerd
2015-09-30 19:04 ` Leonidas Spyropoulos
[not found] ` <1501fba4ad0.2767.ff8c1290f37e89588b661f56613851bb@sjomar.eu>
2015-09-30 19:29 ` Sjoerd
2015-10-01 2:21 ` Duncan
2015-10-01 17:04 ` Sjoerd
2015-10-01 17:46 ` Hugo Mills
2015-10-02 1:11 ` Duncan
2015-10-03 20:53 ` guido_kuenne
2015-10-04 2:28 ` Duncan [this message]
2015-10-04 11:51 ` Sjoerd
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='pan$3b7e2$ac9e4b37$ac602701$c91b77c@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).