From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Patrik Lundquist <patrik.lundquist@gmail.com>,
Chris Murphy <lists@colorremedies.com>
Cc: Stefan K <shadow_7@gmx.net>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs as / filesystem in RAID1
Date: Mon, 4 Feb 2019 12:55:02 -0500 [thread overview]
Message-ID: <b879a985-c991-b4b3-590e-d2aa1a5fa5c5@gmail.com> (raw)
In-Reply-To: <CAA7pwKN9B7LZEo7Op0PndTnU6jo3JdtLi0vdphXZakgbKBB-9w@mail.gmail.com>
On 2019-02-04 12:47, Patrik Lundquist wrote:
> On Sun, 3 Feb 2019 at 01:24, Chris Murphy <lists@colorremedies.com> wrote:
>>
>> 1. At least with raid1/10, a particular device can only be mounted
>> rw,degraded one time and from then on it fails, and can only be ro
>> mounted. There are patches for this but I don't think they've been
>> merged still.
>
> That should be fixed since Linux 4.14.
>
Did the patches that fixed chunk generation land too? Last I knew, 4.14
had the patch that fixed mounting volumes that had this particular
issue, but not the patches that prevented a writable degraded mount from
producing the issue on-disk in the first place.
next prev parent reply other threads:[~2019-02-04 17:55 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
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 [this message]
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=b879a985-c991-b4b3-590e-d2aa1a5fa5c5@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=patrik.lundquist@gmail.com \
--cc=shadow_7@gmx.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.