From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Mount multiple-device-filesystem by UUID
Date: Sun, 28 Jul 2013 08:37:13 +0000 (UTC) [thread overview]
Message-ID: <pan$e00e4$b06f1ef9$18d78546$3ce0429b@cox.net> (raw)
In-Reply-To: pan$b873b$34bc7363$e7fad079$c205b803@cox.net
Duncan posted on Sat, 27 Jul 2013 22:14:02 +0000 as excerpted:
> btrfs raid1 root here, was initr*less until I switched to btrfs which is
> broken with direct-kernel-root-mount rootflags=device=whatever syntax.
>
> UUIDs are indeed userspace -- udev/systemd. However, if your initr*
> includes udev, at least here, it "just works".
>
> I use root=LABEL=whatever here on the kernel commandline for root, and
> LABEL=whatever for non-root in fstab, but as long as udev has the
> directory in /dev/disk/*, mount should work with it, so
> root=UUID=whatever at the kernel commandline should work, as should
> UUID=whatever in fstab as the first field.
I can add...
* I use dracut as my initramfs generator, but with some of the default
modules stripped in ordered to create a leaner initramfs.
* It has a(n optional but obviously activated here) btrfs module that
among other things, runs btrfs device scan before attempting to mount
real-root. That's the critical bit that should be in your initramfs
before attempting to mount a multi-device btrfs. With the btrfs
executable and a call to btrfs device scan, mount, and udev creating the
/dev/disk/by-*/ subdirs, an initramfs environment should really handle
pretty much all the mount options available to you at a full-booted
commandline.
--
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:[~2013-07-28 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 18:50 Mount multiple-device-filesystem by UUID Hendrik Friedel
2013-07-27 18:52 ` Hendrik Friedel
2013-07-27 19:44 ` Hugo Mills
2013-07-27 22:14 ` Duncan
[not found] ` < pan$b873b$34bc7363$e7fad079$c205b803@cox.net>
2013-07-28 8:37 ` Duncan [this message]
2013-07-28 18:57 ` Hendrik Friedel
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$e00e4$b06f1ef9$18d78546$3ce0429b@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).