unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40236@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>,
	Efraim Flashner <efraim@flashner.co.il>,
	Jonathan Brielmaier <jonathan.brielmaier@web.de>
Subject: [bug#40236] [PATCH] doc: Suggest Btrfs with compression instead of ext4 for root partition.
Date: Mon, 01 Jun 2020 01:03:13 -0400	[thread overview]
Message-ID: <87wo4r4bu6.fsf@gmail.com> (raw)
In-Reply-To: <87ftbfreyr.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 31 May 2020 23:07:08 +0200")

Hello Ludovic,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi Pierre,
>
> Pierre Neidhardt <mail@ambrevar.xyz> skribis:
>
>> Now that 37305 is merged, we can revisit this issue.
>>
>> 1. This patch only includes a documentation update.
>> 2. We could make Btrfs the default in the graphical installer.
>> 3. We would probably need to update the tests, at least for the latter.
>>
>> As mentioned above, I think it's safe to enable Btrfs without subvolume,
>> with Zstd compression.
>>
>> For subvolumes, we would need to implement the corresponding tests.
>>
>> Thoughts?
>
> Like I wrote earlier, ext4 is better tested configuration.  For the
> people who take care of the release, believe me, it’s reassuring to have
> one less moving piece.

I believe you! :-)

> So the question is not whether Btrfs is “better”, it’s more about the
> confidence and peace of mind of those responsible for the release and
> subsequent maintenance.
>
> Now, contributions that make Btrfs well-supported in the installer (is
> anything missing there?) and in system tests would be welcome I guess.

I don't know about the installer (I guess there's no support for
configuring Btrfs subvolumes graphically), but for system tests we're
already covered (we have a general Btrfs installation test, as well as
one on a subvolume, even a Btrfs RAID one in patches).

> In the manual, it’s also fine IMO to mention something like:
>
>   Some file systems, such as Btrfs, support compression, which is
>   reported to nicely complement file deduplication that the daemon
>   performs independently of the file system (@pxref{Invoking
>   guix-daemon}).
>
> So a hint for savvy people rather than a recommendation.

That's reasonable as a first step in democratizing Btrfs usage a bit,
without taking any risk, if that's better for your peace of mind :-).

Maxim




  reply	other threads:[~2020-06-01  5:04 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
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 [this message]
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=87wo4r4bu6.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=40236@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=jonathan.brielmaier@web.de \
    --cc=ludo@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).