From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: 02/02: gnu: next: Compress the executable.
Date: Thu, 03 Oct 2019 00:01:43 +0900 [thread overview]
Message-ID: <87eezv9oo8.fsf@gmail.com> (raw)
In-Reply-To: <87a7an8bfy.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sun, 29 Sep 2019 15:43:45 +0200")
Hello Pierre!
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> True.
>
> I've been using Btrfs for my data for a little while and I'm very happy
> with it.
>
> I wonder how Btrfs fares for a Guix system. In many ways, Guix
> supersedes many of the features of Btrfs (snapshots and deduplication in
> particular). So I wonder if it's not redundant and possibly incurs a
> waste of energy.
>
> What's your experience, Maxim?
I like that Btrfs allows to set different namespaces (think of LVM
logical volumes) on the fly as subvolumes. I use snapshots as a mean of
backups, (using the btrfs send/receive mechanism to backup the snapshots
(differentially) to external storage).
I haven't noticed much slow down (if at all?), and the 'lzo' compression
keeps the /gnu/store size 30% smaller or so.
That sums it for now, I think.
HTH!
Maxim
next prev parent reply other threads:[~2019-10-02 15:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190905095602.15524.75425@vcs0.savannah.gnu.org>
[not found] ` <20190905095603.AC57A209A5@vcs0.savannah.gnu.org>
2019-09-05 12:31 ` 02/02: gnu: next: Compress the executable Ricardo Wurmus
2019-09-05 12:51 ` Pierre Neidhardt
2019-09-08 21:19 ` Ludovic Courtès
2019-09-09 8:06 ` Pierre Neidhardt
2019-09-10 12:51 ` Pierre Neidhardt
2019-09-11 20:37 ` Ludovic Courtès
2019-09-12 9:49 ` Pierre Neidhardt
2019-09-16 15:56 ` Ludovic Courtès
2019-09-16 17:46 ` Pierre Neidhardt
2019-09-27 14:35 ` Pierre Neidhardt
2019-09-28 21:02 ` Ludovic Courtès
2019-09-29 7:59 ` Pierre Neidhardt
2019-09-29 13:24 ` Maxim Cournoyer
2019-09-29 13:43 ` Pierre Neidhardt
2019-10-02 7:53 ` Efraim Flashner
2019-10-02 13:27 ` Pierre Neidhardt
2019-10-02 15:01 ` Maxim Cournoyer [this message]
2019-10-02 15:20 ` Pierre Neidhardt
2019-10-02 15:59 ` btrfs and Guix features [was: gnu: next: Compress the executable.] Tobias Geerinckx-Rice
2019-10-02 16:31 ` Pierre Neidhardt
2019-10-02 17:48 ` Tobias Geerinckx-Rice
2019-10-02 18:59 ` Pierre Neidhardt
2019-10-08 4:41 ` Maxim Cournoyer
2019-10-08 7:44 ` Pierre Neidhardt
2019-10-09 1:58 ` Maxim Cournoyer
2019-10-03 7:09 ` 02/02: gnu: next: Compress the executable Efraim Flashner
2019-10-03 18:28 ` Bengt Richter
2019-10-04 8:08 ` Pierre Neidhardt
2019-10-08 7:05 ` Maxim Cournoyer
2019-10-08 7:48 ` Pierre Neidhardt
2019-10-09 1:50 ` Maxim Cournoyer
2019-10-09 8:05 ` Pierre Neidhardt
2020-02-27 15:38 ` Maxim Cournoyer
2020-02-27 15:48 ` Pierre Neidhardt
2020-03-03 5:14 ` Maxim Cournoyer
2020-03-03 9:43 ` Pierre Neidhardt
2020-03-11 2:09 ` Maxim Cournoyer
2020-03-26 8:38 ` Pierre Neidhardt
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=87eezv9oo8.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@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).