Mathieu Othacehe <[email protected]> writes:
> Hello Ricardo, > >> Should we attempt to overwrite /gnu/store and rely exclusively on >> substitutes from the cache? > > Yes, I don't see any other options. Before that, what might be nice > could be: > > 1. Ensure that all Berlin /var/cache/guix/publish directory is > synchronized on Bordeaux. We are now at 117G out of X. We could then > start a publish server on Bordeaux. As Bordeaux is already part of the > default substitute servers list, the transition could be smooth I guess. I had the SAN slice extended from 5TB to 10TB. This is now also full (at 9.2TB due to SAN configuration). I suggest doing the rsync to Bordeaux from /mnt_test/var/cache/guix/publish instead of the much slower /var/cache/guix/publish. It doesn’t hold *all* files, but 9+TB should be enough to fuel the transfer to Bordeaux for a while. > Regarding the /gnu/store re-creation, I wonder how can we do it without > reinstalling completely Berlin. Maybe we could save the system store > closure somewhere and restore it on the shining new file-system? I don’t know. I would want to take a copy of the root file system as a backup of state (like the Lets Encrypt certs), and copy the closure of the current operating system configuration somewhere. We could copy it to a dedicated build node (after stopping the GC cron job) and set it up as an internal substitute server. Then “guix system init” while fetching the substitutes from that server. But I guess we’d have to boot the installer image anyway so that we can safely erase /gnu/store, or else we’d erase files that are currently in use. -- Ricardo
