From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Marius Bakke <mbakke@fastmail.com>, 40236@debbugs.gnu.org
Subject: [bug#40236] [PATCH] doc: Suggest Btrfs with compression instead of ext4 for root partition.
Date: Mon, 04 May 2020 11:22:54 -0400 [thread overview]
Message-ID: <87pnbj3esx.fsf@gmail.com> (raw)
In-Reply-To: <87sgghbiyn.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sun, 03 May 2020 09:01:20 +0200")
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> OK, thanks for the details.
>
> What is "degraded RAID1"?
Degraded RAID1 would be a RAID1 array (mirror disks) in which at least
one drive has failed. As long as at least a single healthy disk
remains, the RAID1 array should remain functional but requires to be
mounted with the 'degraded' mount option (this is done to flag that
there is a serious problem that needs to be addressed, e.g., replace the
faulty drive).
> I'll see if I can test. the patch on my Btrfs system.
> Anything else I can do to help?
Testing on a live system should provide extra confidence that the patch
work as advertised. I have done so on my machines for a while (there's
also a system test), but I'd like to know if it works for someone else
:-).
Maxim
next prev parent reply other threads:[~2020-05-04 15:45 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 8:35 [bug#40236] [PATCH] doc: Suggest Btrfs with compression instead of ext4 for root partition Pierre Neidhardt
2020-03-31 1:52 ` Maxim Cournoyer
2020-03-31 7:52 ` Pierre Neidhardt
2020-03-31 14:53 ` Pierre Neidhardt
2020-03-31 23:20 ` Maxim Cournoyer
2020-04-01 7:00 ` Pierre Neidhardt
2020-05-02 13:29 ` Pierre Neidhardt
2020-05-02 13:50 ` Marius Bakke
2020-05-02 13:58 ` Pierre Neidhardt
2020-05-02 19:03 ` Maxim Cournoyer
2020-05-03 7:01 ` Pierre Neidhardt
2020-05-04 15:22 ` Maxim Cournoyer [this message]
2020-04-01 21:28 ` Ludovic Courtès
2020-04-02 7:15 ` Pierre Neidhardt
2020-04-02 8:04 ` Ludovic Courtès
2020-04-02 10:36 ` Jonathan Brielmaier
2020-04-04 1:28 ` Maxim Cournoyer
2020-04-06 20:20 ` Pierre Neidhardt
2020-04-06 20:42 ` Jonathan Brielmaier
2020-04-07 7:07 ` Pierre Neidhardt
2020-04-08 3:18 ` Maxim Cournoyer
2020-04-09 20:12 ` Efraim Flashner
2020-04-10 7:39 ` Pierre Neidhardt
2020-04-10 8:24 ` Efraim Flashner
2020-04-10 9:04 ` Pierre Neidhardt
2020-04-14 2:20 ` Maxim Cournoyer
2020-04-14 6:53 ` Pierre Neidhardt
2020-05-31 7:39 ` Pierre Neidhardt
2020-05-31 7:55 ` Efraim Flashner
2020-06-01 4:21 ` Maxim Cournoyer
2020-06-01 6:16 ` Efraim Flashner
2020-06-01 7:48 ` Pierre Neidhardt
2020-06-01 18:29 ` Maxim Cournoyer
2020-05-31 21:07 ` Ludovic Courtès
2020-06-01 5:03 ` Maxim Cournoyer
2020-06-02 13:37 ` Pierre Neidhardt
2020-06-03 20:00 ` bug#40236: " Ludovic Courtès
2020-06-04 9:17 ` [bug#40236] " Pierre Neidhardt
2020-06-01 4:49 ` Maxim Cournoyer
2020-03-31 12:09 ` Jonathan Brielmaier
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnbj3esx.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=40236@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
--cc=mbakke@fastmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).