qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Lortie <desrt@desrt.ca>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PATCH: Support for multi-file raw images
Date: Fri, 12 May 2006 17:45:12 -0400	[thread overview]
Message-ID: <1147470312.20722.1.camel@localhost.localdomain> (raw)
In-Reply-To: <4464EE39.6000605@zipman.it>

On Fri, 2006-12-05 at 22:21 +0200, Flavio Visentin wrote:
> OT for qemu, but if you use *rsync*, then only the changed part of the
> file are copied, not all the file. Rsync was written just for this
> reason, to avoid copying unneccessary unchanged data.

But as soon as the modification stamp changes rsync still needs to scan
the entire 20GB file to determine what part has changed.  With two
separate drives on a local system this takes exactly as long as just
copying the entire file.

Cheers

      reply	other threads:[~2006-05-12 21:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11  6:30 [Qemu-devel] PATCH: Support for multi-file raw images Ryan Lortie
2006-05-12 14:35 ` Troy Benjegerdes
2006-05-12 15:54   ` Ryan Lortie
2006-05-12 16:22   ` andrzej zaborowski
2006-05-12 20:21 ` Flavio Visentin
2006-05-12 21:45   ` Ryan Lortie [this message]

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=1147470312.20722.1.camel@localhost.localdomain \
    --to=desrt@desrt.ca \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).