From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Schindelin Subject: Re: [Qemu-devel] qcow2 corruption observed, fixed by reverting old change Date: Thu, 12 Feb 2009 12:08:55 +0100 (CET) Message-ID: References: <20090211070049.GA27821@shareable.org> <4992A108.8070304@suse.de> <20090211114126.GC31997@shareable.org> <4992C77D.4030104@suse.de> <20090212054530.GT27684@sequoia.sous-sol.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Kevin Wolf , Laurent Vivier , kvm-devel To: qemu-devel@nongnu.org Return-path: Received: from mail.gmx.net ([213.165.64.20]:47461 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1756637AbZBLLIJ (ORCPT ); Thu, 12 Feb 2009 06:08:09 -0500 In-Reply-To: <20090212054530.GT27684@sequoia.sous-sol.org> Sender: kvm-owner@vger.kernel.org List-ID: Hi, On Wed, 11 Feb 2009, Chris Wright wrote: > * Kevin Wolf (kwolf@suse.de) wrote: > > I would suspect that simply having a 64 bit host isn't enough to trigger > > the problem. These patches were in for half a year now without anyone > > noticing such failure. > > BTW, we've seen similar corruption, but not narrowed it down successfully as > it's been quite difficult to trigger. Same here, Dscho From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LXZQT-0002BR-0H for qemu-devel@nongnu.org; Thu, 12 Feb 2009 06:08:13 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LXZQQ-0002B5-EE for qemu-devel@nongnu.org; Thu, 12 Feb 2009 06:08:11 -0500 Received: from [199.232.76.173] (port=36355 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LXZQQ-0002B2-7a for qemu-devel@nongnu.org; Thu, 12 Feb 2009 06:08:10 -0500 Received: from mail.gmx.net ([213.165.64.20]:41119) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LXZQP-0001am-Or for qemu-devel@nongnu.org; Thu, 12 Feb 2009 06:08:10 -0500 Date: Thu, 12 Feb 2009 12:08:55 +0100 (CET) From: Johannes Schindelin Subject: Re: [Qemu-devel] qcow2 corruption observed, fixed by reverting old change In-Reply-To: <20090212054530.GT27684@sequoia.sous-sol.org> Message-ID: References: <20090211070049.GA27821@shareable.org> <4992A108.8070304@suse.de> <20090211114126.GC31997@shareable.org> <4992C77D.4030104@suse.de> <20090212054530.GT27684@sequoia.sous-sol.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Cc: Laurent Vivier , Kevin Wolf , kvm-devel Hi, On Wed, 11 Feb 2009, Chris Wright wrote: > * Kevin Wolf (kwolf@suse.de) wrote: > > I would suspect that simply having a 64 bit host isn't enough to trigger > > the problem. These patches were in for half a year now without anyone > > noticing such failure. > > BTW, we've seen similar corruption, but not narrowed it down successfully as > it's been quite difficult to trigger. Same here, Dscho