From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PATCH: Control over drive open modes for backing file
Date: Fri, 01 Aug 2008 10:14:56 -0500 [thread overview]
Message-ID: <48932870.4000507@codemonkey.ws> (raw)
In-Reply-To: <20080801074607.GA12019@shareable.org>
Jamie Lokier wrote:
> Anthony Liguori wrote:
>
>>> Can I arbitrarily branch off different snapshots within a single qcow2
>>> file? Can I delete the 'base' snapshots safely? Most important: what
>>> happens if I have snapshots in a qcow2 file which has a base file, and
>>> I type 'commit'? Does it corrupt all the snapshots, effectively?
>>>
>> snapshots are linear, not branching. And they are only every
>> saved/loaded from the highest level qcow2 file.
>>
>
> So if I understand that right, the 'commit' command (to write to the
> base image) _will_ corrupt all the snapshots since they depend on the
> base image and it just changed??
>
Yes, so don't do that.
BTW, commit is a pretty useless command IMHO. If you use it to save a
snapshot of a disk image while the OS has it mounted, you're not getting
a very good backup.
Regards,
Anthony Liguori
Regards,
Anthony Liguori
> -- Jamie
>
>
>
next prev parent reply other threads:[~2008-08-01 15:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 11:31 [Qemu-devel] PATCH: Control over drive open modes for backing file Daniel P. Berrange
2008-07-31 12:15 ` Jamie Lokier
2008-07-31 13:08 ` Daniel P. Berrange
2008-07-31 13:34 ` Daniel P. Berrange
2008-07-31 13:46 ` Paul Brook
2008-07-31 13:55 ` Daniel P. Berrange
2008-07-31 15:05 ` Blue Swirl
2008-07-31 16:01 ` Jamie Lokier
2008-07-31 16:10 ` Daniel P. Berrange
2008-07-31 18:07 ` Blue Swirl
2008-07-31 14:58 ` Chris Wedgwood
2008-07-31 18:26 ` Anthony Liguori
2008-07-31 18:59 ` Jamie Lokier
2008-07-31 19:37 ` Anthony Liguori
2008-08-01 7:46 ` Jamie Lokier
2008-08-01 15:14 ` Anthony Liguori [this message]
2008-08-01 9:18 ` Daniel P. Berrange
2008-08-01 14:48 ` Anthony Liguori
2008-08-01 16:47 ` Ian Jackson
2008-08-01 17:09 ` Anthony Liguori
2008-08-01 17:10 ` Jamie Lokier
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=48932870.4000507@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).