unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 40236@debbugs.gnu.org
Subject: [bug#40236] [PATCH] doc: Suggest Btrfs with compression instead of ext4 for root partition.
Date: Mon, 30 Mar 2020 21:52:43 -0400	[thread overview]
Message-ID: <87h7y5z3x0.fsf@gmail.com> (raw)
In-Reply-To: <20200326083524.20275-1-mail@ambrevar.xyz> (Pierre Neidhardt's message of "Thu, 26 Mar 2020 09:35:24 +0100")

Hi!

Pierre Neidhardt <mail@ambrevar.xyz> writes:

> * gnu/system/examples/desktop.tmpl: Adjust root file-system to use Btrfs.
> ---
>  gnu/system/examples/desktop.tmpl | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/system/examples/desktop.tmpl b/gnu/system/examples/desktop.tmpl
> index 3931bad60d..e61e8064cd 100644
> --- a/gnu/system/examples/desktop.tmpl
> +++ b/gnu/system/examples/desktop.tmpl
> @@ -34,7 +34,8 @@
>                   (list (file-system
>                           (device (file-system-label "my-root"))
>                           (mount-point "/")
> -                         (type "ext4")
> +                         (type "btrfs")
> +                         (options "subvol=rootfs,compress=zstd")
>                           (dependencies mapped-devices))
>                         (file-system
>                           (device (uuid "1234-ABCD" 'fat))

I think Btrfs with compression is a fine, modern default of a file
system, but we shall get a good samples of opinions (I expect a variety
of them :-)) and common agreement before pushing this change.

For those wondering about the benefits of having the root file system on
a subvolume (named 'rootfs' in the proposed configuration), the
following page [0] explains it as:

     [...] The above layout, which obviously serves as the system's
     "main" filesystem, places data directly within the top-level
     subvolume (namely everything for example /usr, that's not in a
     child subvolume) This makes changing the structure (for example to
     something more flat) more difficult, which is why it's generally
     suggested to place the actual data in a subvolume (that is not the
     top-level subvolume), in the above example, a better layout would
     be the following:

     toplevel                        (volume root directory, not mounted)
       \-- root                      (subvolume root directory, to be mounted at /)
           +-- home                  (subvolume root directory)
           +-- var                   (subvolume root directory)
               +-- www               (subvolume root directory)
               +-- lib               (directory)
                    \-- postgresql   (subvolume root directory)

In short, it allows exposing just the subvolumes which should be
visible, instead of everything.


I've marked this blocked by 37305, which includes GRUB support for
booting from a subvolume as well as documentation about Btrfs usage in
Guix.

[0]  https://btrfs.wiki.kernel.org/index.php/SysadminGuide#Layout

  reply	other threads:[~2020-03-31  1:53 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 [this message]
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
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=87h7y5z3x0.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=40236@debbugs.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).