From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Fast checksumming of whole partitions
Date: Fri, 11 Jun 2010 23:41:02 +0100 [thread overview]
Message-ID: <201006112341.15482.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20100607185404.GB5128@solfire>
[-- Attachment #1: Type: Text/Plain, Size: 1860 bytes --]
On Monday 07 June 2010 19:54:04 meino.cramer@gmx.de wrote:
> Andrea Conti <alyf@alyf.net> [10-06-07 20:28]:
> > > Does anyone has experiences with gparted?
> >
> > I have no experience with Parted Magic, but I have used a lot the
> > Gparted live CD (http://gparted.sourceforge.net/livecd.php). No idea on
> > how the two compare.
> >
> > As for gparted (which is a lot more than a gui for parted), I have used
> > it on ext4 a couple of times and it managed to complete the copy without
> > destroying anything, so I'd say it works. On the other hand, I copied
> > *lots* of ext3 and ntfs partitions, and it never failed me.
> >
> > BTW, by default gparted does *not* do sector-by-sector partition copies.
> > In my opinion this is a much better approach if you do not need a
> > bit-exact copy of the original (e.g. if you're doing forensics or
> > debugging filesystems), but in the end it's up to you.
> >
> > andrea
>
> Hi Andreas,
>
> do I understand right here:
> Instead of using dcfldd or simply dd to copy one disk to
> another for backup reasons it is much better/faster to use gparted
> to simply copy all partitions from sda to sdb using sda1=>sdb1,
> sda2=>sdb2,... and so forth?
> Is there something like a "batch job" or scripting interface
> for gparted so that I can give gparted the complete copy job
> once, go to sleep and next moring the copy is done?
> Is gparted able to shut down the system after finishing its
> work or to end itsself so a little script can detect the
> job is done and halt the system then?
Am I being old-fashioned, or is there anything wrong with rsync (if not
tar/star) for this purpose? Make sure to add the relevant option for sparse
files and only bits and bytes with data will be copied over. Therefore it
will be faster than dd at any rate.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-11 22:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 6:39 [gentoo-user] Fast checksumming of whole partitions meino.cramer
2010-06-05 7:19 ` [gentoo-user] " Nikos Chantziaras
2010-06-07 15:48 ` meino.cramer
2010-06-07 17:10 ` walt
2010-06-07 18:47 ` meino.cramer
2010-06-07 17:31 ` Andrea Conti
2010-06-07 18:54 ` meino.cramer
2010-06-11 22:41 ` Mick [this message]
2010-06-05 7:32 ` [gentoo-user] " Andrea Conti
2010-06-05 17:39 ` [gentoo-user] " 7v5w7go9ub0o
2010-06-05 19:23 ` meino.cramer
2010-06-05 20:11 ` Manuel Klemenz
2010-06-06 19:02 ` 7v5w7go9ub0o
2010-06-06 19:47 ` Joerg Schilling
2010-06-06 22:43 ` 7v5w7go9ub0o
2010-06-06 23:12 ` Joerg Schilling
2010-06-06 22:46 ` Neil Bothwick
2010-06-07 1:04 ` 7v5w7go9ub0o
2010-06-05 23:44 ` 7v5w7go9ub0o
2010-06-06 10:19 ` Andrea Conti
2010-06-06 16:55 ` Mick
2010-06-06 18:55 ` 7v5w7go9ub0o
2010-06-06 20:00 ` Mick
2010-06-06 20:45 ` Andrea Conti
2010-06-06 23:06 ` 7v5w7go9ub0o
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=201006112341.15482.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@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