From: Chris Murphy <lists@colorremedies.com>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
waxhead <waxhead@dirtcellar.net>, Stefan K <shadow_7@gmx.net>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs as / filesystem in RAID1
Date: Mon, 11 Feb 2019 14:15:35 -0700 [thread overview]
Message-ID: <CAJCQCtT27ONP4W30Q220OEHyXmypMM0oqng6sbRwzm9JJ3k8EA@mail.gmail.com> (raw)
In-Reply-To: <a8e00ae7-9e18-ba74-5521-a2db7b525e51@gmail.com>
On Mon, Feb 11, 2019 at 5:17 AM Austin S. Hemmelgarn
<ahferroin7@gmail.com> wrote:
>
> Last I knew, it was systemd itself doing the pause, because we provide
> no real device for udev to wait on appearing.
Well there's more than one thing responsible for the net behavior. The
most central thing waiting is the kernel. And that's because 'btrfs
device ready' simply waits until all devices are found (by kernel
code). That's the command that /usr/lib/udev/rules.d/64-btrfs.rules
calls. So it is also udev that doesn't return from that, indefinitely
as far as I know. And therefore systemd won't issue a mount command
for sysroot.
--
Chris Murphy
next prev parent reply other threads:[~2019-02-11 21:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 10:28 btrfs as / filesystem in RAID1 Stefan K
2019-02-01 19:13 ` Hans van Kranenburg
2019-02-07 11:04 ` Stefan K
2019-02-07 12:18 ` Austin S. Hemmelgarn
2019-02-07 18:53 ` waxhead
2019-02-07 19:39 ` Austin S. Hemmelgarn
2019-02-07 21:21 ` Remi Gauvin
2019-02-08 4:51 ` Andrei Borzenkov
2019-02-08 12:54 ` Austin S. Hemmelgarn
2019-02-08 7:15 ` Stefan K
2019-02-08 12:58 ` Austin S. Hemmelgarn
2019-02-08 16:56 ` Chris Murphy
2019-02-08 18:10 ` waxhead
2019-02-08 19:17 ` Austin S. Hemmelgarn
2019-02-09 12:13 ` waxhead
2019-02-10 18:34 ` Chris Murphy
2019-02-11 12:17 ` Austin S. Hemmelgarn
2019-02-11 21:15 ` Chris Murphy [this message]
2019-02-08 20:17 ` Chris Murphy
2019-02-07 17:15 ` Chris Murphy
2019-02-07 17:37 ` Martin Steigerwald
2019-02-07 22:19 ` Chris Murphy
2019-02-07 23:02 ` Remi Gauvin
2019-02-08 7:33 ` Stefan K
2019-02-08 17:26 ` Chris Murphy
2019-02-11 9:30 ` Anand Jain
2019-02-02 23:35 ` Chris Murphy
2019-02-04 17:47 ` Patrik Lundquist
2019-02-04 17:55 ` Austin S. Hemmelgarn
2019-02-04 22:19 ` Patrik Lundquist
2019-02-05 6:46 ` Chris Murphy
2019-02-05 7:37 ` 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=CAJCQCtT27ONP4W30Q220OEHyXmypMM0oqng6sbRwzm9JJ3k8EA@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=shadow_7@gmx.net \
--cc=waxhead@dirtcellar.net \
/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).