From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: "Pierre Neidhardt" <mail@ambrevar.xyz>,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: 40236@debbugs.gnu.org
Subject: [bug#40236] [PATCH] doc: Suggest Btrfs with compression instead of ext4 for root partition.
Date: Mon, 6 Apr 2020 22:42:09 +0200 [thread overview]
Message-ID: <c9bde2d4-01ba-4827-f667-05b83d66d66e@web.de> (raw)
In-Reply-To: <87r1x0welb.fsf@ambrevar.xyz>
On 06.04.20 22:20, Pierre Neidhardt wrote:> Jonathan Brielmaier wrote on
Tue Mar 31 14:09:04+0200 2020
>>> * gnu/system/examples/desktop.tmpl: Adjust root file-system to use Btrfs.
>>
>> I would oppose this change as I had too much troubles with Btrfs on my
>> openSUSE machines. I used a simple partition layout spanning the whole
>> disk. AFAIK this is not really recommended with btrfs. My laptop was
>> from time to time unusable until I reinstalled it with ext4...
>
> This is for Guix System only. Did you mean that it would be problematic
> if you were running openSUSE in dual boot?
No, I did run openSUSE on btrfs, there was no Guix involved at all. But
btrfs seemed to be the root case of all my troubles (performance,
hang-ups etc).
>> Further do we need all this rollback stuff from btrfs if we have it
>> already in Guix?
>
> Btrfs has many benefits over Ext3:
>
> it offers compression to about 30% on average, it supports subvolumes,
> snapshots and snapshot syncing, and much more.
Snapshots did fill up my disk. I had no use for them on my laptop. On a
Guix System even less, because you have rollbacks from the package
manager :)
> For all these reasons I believe Btrfs is a good default for the OSes of tomorrow! :)
So maybe create a config for the OSes of tomorrow: btrfs, wireguard,
rust etc :P
next prev parent reply other threads:[~2020-04-06 20:43 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c9bde2d4-01ba-4827-f667-05b83d66d66e@web.de \
--to=jonathan.brielmaier@web.de \
--cc=40236@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=maxim.cournoyer@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.