all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: carl hansen <carlhansen1234@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: moving /gnu to different disk
Date: Tue, 12 Jan 2016 17:29:02 -0500	[thread overview]
Message-ID: <20160112222902.GA5739@jasmine> (raw)
In-Reply-To: <CAHEkXCTOUkua=P1+ChHJ6D9UfOnS_kzdCsoEGDMU=gj7rcAAFQ@mail.gmail.com>

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`. Of course you
should test that it works as expected first or you might end up out of
space on the new device, too!

From the rsync man page:
-H, --hard-links            preserve hard links

Of course, there may be a better solution altogether.

> 
> Are my fears founded? How to proceed?
> Or better to start over with new installation of gnux and /gnu?

  reply	other threads:[~2016-01-12 22:29 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 [this message]
2016-01-13 11:12   ` Ludovic Courtès
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=20160112222902.GA5739@jasmine \
    --to=leo@famulari.name \
    --cc=carlhansen1234@gmail.com \
    --cc=help-guix@gnu.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.
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.