From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LBz7q-0004Aa-Sz for qemu-devel@nongnu.org; Sun, 14 Dec 2008 17:07:46 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LBz7p-00049l-7S for qemu-devel@nongnu.org; Sun, 14 Dec 2008 17:07:46 -0500 Received: from [199.232.76.173] (port=53199 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBz7p-00049h-4b for qemu-devel@nongnu.org; Sun, 14 Dec 2008 17:07:45 -0500 Received: from main.gmane.org ([80.91.229.2]:59418 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LBz7o-0003ZM-OF for qemu-devel@nongnu.org; Sun, 14 Dec 2008 17:07:44 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LBz7j-0001VD-Ck for qemu-devel@nongnu.org; Sun, 14 Dec 2008 22:07:39 +0000 Received: from adsl-69-234-198-192.dsl.irvnca.pacbell.net ([69.234.198.192]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 14 Dec 2008 22:07:39 +0000 Received: from w41ter by adsl-69-234-198-192.dsl.irvnca.pacbell.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 14 Dec 2008 22:07:39 +0000 From: walt Date: Sun, 14 Dec 2008 14:07:31 -0800 Message-ID: References: <20081214181252.GE28984@shareable.org> <20081214183509.GB2995@networkno.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <20081214183509.GB2995@networkno.de> Sender: news Subject: [Qemu-devel] Re: snapshot vs COW? Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Thiemo Seufer wrote: > Jamie Lokier wrote: >> walt wrote: >>> 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... Glad to hear it, thanks for the update. That means that the fix is already in the kvm git repository?