From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57924) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S0Uir-0002Q8-Gj for qemu-devel@nongnu.org; Thu, 23 Feb 2012 04:12:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S0Uim-0007eW-UT for qemu-devel@nongnu.org; Thu, 23 Feb 2012 04:12:21 -0500 Received: from mail-ey0-f173.google.com ([209.85.215.173]:49668) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S0Uim-0007eQ-IS for qemu-devel@nongnu.org; Thu, 23 Feb 2012 04:12:16 -0500 Received: by eaac1 with SMTP id c1so409614eaa.4 for ; Thu, 23 Feb 2012 01:12:15 -0800 (PST) Date: Thu, 23 Feb 2012 09:12:12 +0000 From: Stefan Hajnoczi Message-ID: <20120223091212.GA10575@stefanha-thinkpad.localdomain> References: <20120222214959.20738.46143.malonedeb@soybean.canonical.com> <20120222214959.20738.46143.malonedeb@soybean.canonical.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120222214959.20738.46143.malonedeb@soybean.canonical.com> Subject: Re: [Qemu-devel] [Bug 939027] [NEW] Combining direct_io and non-direct_io leads to hang List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avleen Vig <939027@bugs.launchpad.net> Cc: qemu-devel@nongnu.org On Wed, Feb 22, 2012 at 09:49:59PM -0000, Avleen Vig wrote: > Version 0.12.2 - I know this isn't the latest but I looked through the > changelogs and couldn't find any references to this being fixed. > > This is related to issues that many apps have, and is described in more detail here: > http://oss.sgi.com/archives/xfs/2010-07/msg00163.html > and: > https://bugs.launchpad.net/percona-xtrabackup/+bug/606981 > > When using both direct io and buffered io on the same file, you can cause corruption on the filesystem and other issues. > XFS out right hangs, but the problem exists on ext3 and other filesystems which silently carry on. > > **this is a data corruption issue**. > > This is the full stack trace we got from a recent hang: I only see qemu-kvm in the backtrace. QEMU normally only access the image file either with or without O_DIRECT - not both at the same time. Were you running another program that accesses the image file at the same time? Stefan