public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: Cloning a system drive
Date: Sun, 7 Oct 2007 09:33:54 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.10.07.09.33.54@cox.net> (raw)
In-Reply-To: 7c08b4dd0710062149p7c7548aai7ba062ea4e17d2a3@mail.gmail.com

"Peter Davoust" <worldgnat@gmail.com> posted
7c08b4dd0710062149p7c7548aai7ba062ea4e17d2a3@mail.gmail.com, excerpted
below, on  Sun, 07 Oct 2007 00:49:11 -0400:

> This may be a little noobish, and it may have been said, but can't you
> just install the new drive, partition it identically to the original
> drive and then...
> 
> dd if=/dev/hda1 of=/dev/hdb1
> dd if=/dev/hda2 of=/dev/hdb2
> 
> so on and so forth until you've got everything copied? Or event just
> 
> dd if=/dev/hda of=/dev/hdb
> 
> Wouldn't that work?

It should, you're right.

However, that's a direct image straight across, fragmented files, even 
filesystem corruption if it exists on the source, and it's nice to take 
the opportunity to copy file-by file so everything gets defragmented and 
all the file nodes get organized, if possible, particularly since few 
Linux filesystems /have/ a defrag.  Few need it very badly as long as a 
decent amount of free-space is kept on each filesystem (50% is great, 25% 
minimum for best operation, 10% and performance /does/ start to suffer), 
but it's still nice to organize it, getting files all in one piece and 
directories all located together, while one can.

Also, new drives are generally larger and it's nice to be able to take 
the opportunity to reorganize the partitions.

All those are reasons I like my simple partition/mkfs/copy-the-files-over 
method, but some folks don't seem to like that idea for whatever reason.  
<shrug>

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2007-10-07  9:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 20:58 [gentoo-amd64] Cloning a system drive Mark Knecht
2007-10-05 21:14 ` Dieter Ries
2007-10-05 22:46 ` Drake Donahue
2007-10-05 23:07   ` Mark Knecht
2007-10-06  1:00     ` Drake Donahue
2007-10-06 12:22     ` Dieter Ries
2007-10-06  1:53 ` [gentoo-amd64] " Duncan
2007-10-06  2:35   ` Richard Freeman
2007-10-06  2:43     ` Mark Knecht
2007-10-06 12:47       ` Duncan
2007-10-06 13:16         ` Mark Knecht
2007-10-07  3:58           ` Drake Donahue
2007-10-07  4:49             ` Peter Davoust
2007-10-07  9:33               ` Duncan [this message]
2007-10-07 18:34               ` Brian Litzinger
2007-10-08  9:17                 ` Beso
2007-10-08 16:17                   ` Brian Litzinger
2007-10-08 16:28                     ` Mark Knecht
2007-10-08 16:43                     ` Beso
2007-10-08 22:39                       ` Peter Davoust

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=pan.2007.10.07.09.33.54@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.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