From: "Ludovic Courtès" <ludo@gnu.org>
To: Jack Hill <jackhill@jackhill.us>
Cc: 51427@debbugs.gnu.org,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#51427] [PATCH] nix: libstore: Do not remove unused links when deleting specific items.
Date: Tue, 09 Nov 2021 13:56:35 +0100 [thread overview]
Message-ID: <87lf1xmqrg.fsf_-_@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2111082329280.4243@marsh.hcoop.net> (Jack Hill's message of "Mon, 8 Nov 2021 23:57:23 -0500 (EST)")
Hi,
Jack Hill <jackhill@jackhill.us> skribis:
> On Mon, 8 Nov 2021, Maxim Cournoyer wrote:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> BTW, those using Btrfs can probably use ‘--disable-deduplication’ and be
>>> done with it.
>>
>> I erroneously used to think that Btrfs could do live deduplication, but
>> it doesn't. There are external tools to do out of band / batch
>> deduplication though [0]; so if they perform better than the guix daemon's
>> own dedup, perhaps we could document this way out for our Btrfs users.
>>
>> [0] https://btrfs.wiki.kernel.org/index.php/Deduplication
>
> A little while ago I had hoped to test btrfs with
> --disable-deduplication and bees [1] as the deduplication agent, but
> wasn't able to successfully run a system with --disable-deduplication
> because I needed the deduplication to cover up problem with grafts
> [2]. Until we resolve the second issue, I don't think we should
> recommend folks run the daemon with --disable-deduplication.
>
> [1] https://issues.guix.gnu.org/47983 (still missing a service)
> [2] https://issues.guix.gnu.org/47115
Oh, right. We didn’t quite get to the bottom of #2. Is it still an
issue? Some questions remained opened.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-11-09 12:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 3:49 [bug#51427] [PATCH] nix: libstore: Do not remove unused links when deleting specific items Maxim Cournoyer
2021-10-28 14:16 ` Ludovic Courtès
2021-10-31 8:50 ` Liliana Marie Prikler
2021-10-31 14:07 ` Ludovic Courtès
2021-10-31 14:39 ` Liliana Marie Prikler
2021-10-31 20:51 ` Maxim Cournoyer
2021-11-03 10:45 ` zimoun
2021-11-06 16:57 ` Ludovic Courtès
2021-11-09 4:11 ` Maxim Cournoyer
2021-11-09 4:57 ` Jack Hill
2021-11-09 12:56 ` Ludovic Courtès [this message]
2021-11-09 18:10 ` zimoun
2021-11-17 10:02 ` Ludovic Courtès
2021-11-17 11:49 ` zimoun
2022-07-18 13:57 ` Ludovic Courtès
2022-07-18 17:03 ` Liliana Marie Prikler
2022-07-19 8:34 ` Ludovic Courtès
2022-07-19 18:42 ` Liliana Marie Prikler
2022-07-19 19:25 ` Tobias Geerinckx-Rice via Guix-patches via
2022-07-21 9:21 ` Ludovic Courtès
2022-07-21 18:02 ` Liliana Marie Prikler
2022-07-22 12:14 ` Ludovic Courtès
2022-07-22 13:39 ` Maxime Devos
2022-07-22 23:07 ` Ludovic Courtès
2022-07-23 6:52 ` Liliana Marie Prikler
2022-07-23 10:24 ` Maxime Devos
2023-06-12 20:55 ` Felix Lechner via Guix-patches via
2023-06-13 4:26 ` Liliana Marie Prikler
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=87lf1xmqrg.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=51427@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
--cc=liliana.prikler@gmail.com \
--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 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).