qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: snapshot vs COW?
Date: Sun, 14 Dec 2008 19:35:09 +0100	[thread overview]
Message-ID: <20081214183509.GB2995@networkno.de> (raw)
In-Reply-To: <20081214181252.GE28984@shareable.org>

Jamie Lokier wrote:
> walt wrote:
> > Jun Koi wrote:
> > >Hi,
> > >
> > > From what I see, both snapshot and COW features can be used to try
> > >some changes on the file image before we the change back to the
> > >original image.
> > >
> > >But what is the advantages of snapshot over COW, and in which case we
> > >should use snapshot, but not COW? Vice verse, when COW is more
> > >appropriate?
> > >
> > >Many thanks,
> > >Jun
> > 
> > COW is a nice feature but it is currently broken, so don't use it
> > until it gets fixed.  When you commit any changes your backing file
> > will be corrupted.
> 
> Aieee!  I use COW instead of snapshots in my management scripts,
> because snapshots are harder to manage.
> 
> Is the COW brokenness documented?  What version did it start being broken?

Cow2 is broken in the 0.9.1 release, it was fixed shortly afterwards.
The symptom was corruption of the image when it grew beyond 4 GB.

AFAIK you can still break cow2 images by running out of disk space.
This is the case since cow2 suport was written.


Thiemo

  reply	other threads:[~2008-12-14 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12  3:17 [Qemu-devel] snapshot vs COW? Jun Koi
2008-12-12  3:18 ` [Qemu-devel] " Jun Koi
2008-12-12 13:25 ` walt
2008-12-14 18:12   ` Jamie Lokier
2008-12-14 18:35     ` Thiemo Seufer [this message]
2008-12-14 22:07       ` walt

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=20081214183509.GB2995@networkno.de \
    --to=ths@networkno.de \
    --cc=jamie@shareable.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).