From: Andrei Borzenkov <arvidjaar@gmail.com>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
waxhead@dirtcellar.net, Stefan K <shadow_7@gmx.net>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs as / filesystem in RAID1
Date: Fri, 8 Feb 2019 07:51:04 +0300 [thread overview]
Message-ID: <df1bde98-8849-581a-8f96-3a2045fe6274@gmail.com> (raw)
In-Reply-To: <c8708ebd-c6c2-6916-6da2-5b415c0585e4@gmail.com>
07.02.2019 22:39, Austin S. Hemmelgarn пишет:
> The issue with systemd is that if you pass 'degraded' on most systemd
> systems, and devices are missing when the system tries to mount the
> volume, systemd won't mount it because it doesn't see all the devices.
> It doesn't even _try_ to mount it because it doesn't see all the
> devices. Changing to degraded by default won't fix this, because it's a
> systemd problem.
>
Oh no, not again. It was discussed millions of times already - systemd
is using information that btrfs provides.
> The same issue also makes it a serious pain in the arse to recover
> degraded BTRFS volumes on systemd systems, because if the volume is
> supposed to mount normally on that system, systemd will unmount it if it
> doesn't see all the devices, regardless of how it got mounted in the
> first place.
>
*That* would be systemd issue indeed. If someone can reliably reproduce
it, systemd bug report would certainly be in order.
next prev parent reply other threads:[~2019-02-08 4:51 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 [this message]
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
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=df1bde98-8849-581a-8f96-3a2045fe6274@gmail.com \
--to=arvidjaar@gmail.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 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.