From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: moving /gnu to different disk
Date: Wed, 13 Jan 2016 12:12:50 +0100 [thread overview]
Message-ID: <878u3t7mx9.fsf@gnu.org> (raw)
In-Reply-To: <20160112222902.GA5739@jasmine> (Leo Famulari's message of "Tue, 12 Jan 2016 17:29:02 -0500")
Leo Famulari <leo@famulari.name> skribis:
> On Tue, Jan 12, 2016 at 01:39:02PM -0800, carl hansen wrote:
>> Rather than trying the following, I thought, "Why not ask first?"
>>
>> Due to the sizes of various hard disks in my machine, I want to move /gnu
>> to /directoryondifferentdisk/gnu
>> and then do
>> mount --bind /directoryondifferentdisk/gnu /gnu
>>
>> (I have already formed a superstition that
>> ln -s /directoryondifferentdisk/gnu /gnu
>> won't work)
>>
>> I see a vast collection of hard links in /gnu/store/.links...
>>
>> I forsee problems when copying /gnu, not reproducing hard links
>> but reproducing the data.
>
> You could try moving the data with `rsync --hard-links`.
In fact you can also omit /gnu/store/.links when copying. Nothing is
lost by doing so. This directory simply contains a hash-to-file mapping
used by the deduplication mechanism.
However, make sure do copy /var/guix in addition to /gnu/store!
/var/guix/db/db.sqlite is the database containing meta-data for
/gnu/store, so things will break badly if it’s missing or out-of-sync.
HTH,
Ludo’.
next prev parent reply other threads:[~2016-01-13 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 21:39 moving /gnu to different disk carl hansen
2016-01-12 22:29 ` Leo Famulari
2016-01-13 11:12 ` Ludovic Courtès [this message]
2016-01-12 22:29 ` Andreas Enge
2016-01-13 4:31 ` carl hansen
2016-01-13 11:14 ` Efraim Flashner
2016-01-15 14:06 ` Mark H Weaver
2016-01-13 18:06 ` Christopher Allan Webber
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878u3t7mx9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.