unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Phil <phil@beadling.co.uk>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Moving /gnu/store safely?
Date: Wed, 03 Mar 2021 20:14:46 +0000	[thread overview]
Message-ID: <85im68m1uf.fsf@beadling.co.uk> (raw)
In-Reply-To: <878s74yyyy.fsf@nckx>

Thanks v much for the explanations.

Tobias Geerinckx-Rice writes:

> As gremlin's go this one is pretty tame, even cuddly: the Guix daemon
> deduplicates identical files, and creates hard links instead, saving a
> good amount of space.  That's all.
>
> By default, rsync does not preserve hard links (because of potential

Heh heh - yes I was surprised (and relieved) how quickly this gremlin
was dealt with just by scanning the manual and throwing some commands
together - this makes perfect sense so each hardlink just becomes a new file on the target.

I'm assuming the doubling in size is more fluke than by design?
i.e. there is no reason to assume each file is duplicated exactly once
in Guix?  It just turns out that hard linking was saving approx 50% by
chance in my specific store - it could have been 30% or 70% or whatever
and depends on your store contents?

> No, the links were *lost* and replaced by separate files during
> rsyncing.
>

Got it.  At the risk of speculating, would you expect the subsequent
execution of the garbage collector to deduplicate the identical rsync'd files
again?  I'm 100% clear on why the problem happened, just want to check I
understand why it went away which I ran 'guix gc'.

If I look at the link count on the files in my new /gnu/store I can see
some files have a count >1, which certainly suggests that Guix has
performed some sort of deduplication after the rsync?




      reply	other threads:[~2021-03-03 20:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 13:44 Moving /gnu/store safely? Phil
2021-03-03 13:49 ` Julien Lepiller
2021-03-03 14:49 ` André Batista
2021-03-03 19:10   ` Phil
2021-03-03 16:38 ` Tobias Geerinckx-Rice
2021-03-03 20:14   ` Phil [this message]

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=85im68m1uf.fsf@beadling.co.uk \
    --to=phil@beadling.co.uk \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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.
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).