From: Troy Benjegerdes <hozer@hozed.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PATCH: Support for multi-file raw images
Date: Fri, 12 May 2006 09:35:22 -0500 [thread overview]
Message-ID: <20060512143517.GL15855@narn.hozed.org> (raw)
In-Reply-To: <1147329045.17542.15.camel@moonpix.desrt.ca>
On Thu, May 11, 2006 at 02:30:45AM -0400, Ryan Lortie wrote:
> Hello.
>
> Attached is a C file (and small patch) to add support for multi-file raw
> images to QEMU. The rationale (for me at least) is as follows:
>
> I use rsync to backup my home directory. The act of starting up QEMU
> changes a 20GB file on my drive. This causes 20GB of extra copying next
> time I do backups. If I could split the drive image into smaller parts
> (maybe 2048 10MB files) then the amount of extra copying is drastically
> reduced (since only a few of these files are modified).
>
> There are definitely other reasons that this may be useful.
Have you tried making a read-only 'base' image and using qcow images
instead? I'm not convinced that splitting things up is going to help a
lot. You might end up writing 1 512 byte block each to 500 files.. in
the qcow image case, that is writing 256K, and with 10mb files, that's
5GB.
> o If the files comprising the device are deleted (for example) while
> QEMU is running then this is quite bad. Currently this will result
> in read/write requests returning -1. Maybe it makes sense to panic
> and cause QEMU to exit.
>
at the very least, the console should print an error. If you can keep
all the files open, deleting the file won't be a problem.
next prev parent reply other threads:[~2006-05-12 14:35 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 [this message]
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
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=20060512143517.GL15855@narn.hozed.org \
--to=hozer@hozed.org \
--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).