From: swedebugia <swedebugia@riseup.net>
To: Mark H Weaver <mhw@netris.org>, Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-Help <help-guix@gnu.org>
Subject: Re: Ever-growing store with --gc-keep-outputs?
Date: Fri, 9 Nov 2018 07:53:57 +0100 [thread overview]
Message-ID: <34cb1281-438a-3a0b-44a1-afaa7d57487b@riseup.net> (raw)
In-Reply-To: <87o9d0geez.fsf@netris.org>
Hi
On 2018-09-14 19:46, Mark H Weaver wrote:
> Hi Pierre,
>
> Pierre Neidhardt <mail@ambrevar.xyz> writes:
>
>>> If, say, “coreutils” is live, then the corresponding “coreutils.drv”
>>> will be considered live as well when you pass --gc-keep-derivations.
>> Is the .drv live forever then? Even when all the corresponding outputs have
>> been deleted from all profiles / generations?
> No, certainly not. To expand on what Ludovic wrote, by passing
> --gc-keep-derivations, you are providing an additional way for a .drv to
> be reachable from your GC roots. The .drv file will be kept alive for
> as long as any of its outputs are kept alive. More generally, it will
> be kept alive as long as anything that was built upon it is kept alive.
> That does not imply that .drv files are kept alive forever.
>
> I've been using --gc-keep-derivations=yes and --gc-keep-outputs=yes for
> a long time, and it works well in my preferred mode of operation where I
> build everything locally and never use substitutes. It ensures that
> everything needed to build my GC-root-protected store items will be kept
> alive.
Interesting setup. Would you be willing to share the amount of space
consumed by this mode?
How many packages do you use?
Are you willing to share your config also?
> When I want to free up some disk space, I do the following steps:
>
> (1) update my user profiles and delete old generations
> (2) delete older generations in /var/guix/profiles (but always
> keeping the one referenced by /run/booted-system!)
> (3) reconfigure the system to remove the old system profiles from
> grub.cfg
> (4) guix gc
This would be nice to have in the manual I think.
--
Cheers Swedebugia
next prev parent reply other threads:[~2018-11-09 6:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 19:11 Ever-growing store with --gc-keep-outputs? Pierre Neidhardt
2018-09-12 10:55 ` Pierre Neidhardt
2018-09-13 9:09 ` Ludovic Courtès
2018-09-13 9:32 ` Pierre Neidhardt
2018-09-14 9:51 ` Ludovic Courtès
2018-09-14 10:57 ` Pierre Neidhardt
2018-09-14 17:46 ` Mark H Weaver
2018-09-14 18:02 ` Pierre Neidhardt
2018-09-14 21:34 ` Mark H Weaver
2018-09-14 22:10 ` Pierre Neidhardt
2018-11-09 6:53 ` swedebugia [this message]
2018-11-09 7:13 ` Mark H Weaver
2018-11-09 10:58 ` Pierre Neidhardt
2018-11-09 16:47 ` swedebugia
2018-11-13 20:31 ` Leo Famulari
2018-11-13 21:14 ` swedebugia
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=34cb1281-438a-3a0b-44a1-afaa7d57487b@riseup.net \
--to=swedebugia@riseup.net \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=mhw@netris.org \
/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).