From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: raw disks no longer work in latest kvm (kvm-88 was fine) Date: Sun, 07 Mar 2010 12:32:38 +0300 Message-ID: <4B9372B6.3050408@msgid.tls.msk.ru> References: <4B92BF97.4040001@nagafix.co.uk> <4B92C90B.4030807@msgid.tls.msk.ru> <4B932829.8090503@nagafix.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Antoine Martin Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:40720 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753037Ab0CGJcl (ORCPT ); Sun, 7 Mar 2010 04:32:41 -0500 In-Reply-To: <4B932829.8090503@nagafix.co.uk> Sender: kvm-owner@vger.kernel.org List-ID: Antoine Martin wrote: [] >> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2933400&group_id=180599 >> >> > The initial report is almost 8 weeks old! > Is data-corruption and data loss somehow less important than the > hundreds of patches that have been submitted since?? Or is there a fix > somewhere I've missed? I can only guess that the info collected so far is not sufficient to understand what's going on: except of "I/O error writing block NNN" we does not have anything at all. So it's impossible to know where the problem is. Please don't blame on people (me included: i suffer from this same issue just like you). We need something constructive. And by the way, as stated in my comment attached to that bug (I'm user mjtsf at sourceforge), error-behavour=remount-ro avoids data corruption (this is not unique for the issue in question but for general case of i/o errors and filesystem operations). /mjt