From: Stefan Hajnoczi <stefanha@gmail.com>
To: Avleen Vig <939027@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 939027] [NEW] Combining direct_io and non-direct_io leads to hang
Date: Thu, 23 Feb 2012 09:12:12 +0000 [thread overview]
Message-ID: <20120223091212.GA10575@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <20120222214959.20738.46143.malonedeb@soybean.canonical.com>
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
next prev parent reply other threads:[~2012-02-23 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 21:49 [Qemu-devel] [Bug 939027] [NEW] Combining direct_io and non-direct_io leads to hang Avleen Vig
2012-02-23 9:12 ` Stefan Hajnoczi [this message]
2012-02-23 21:39 ` [Qemu-devel] [Bug 939027] " Avleen Vig
2012-02-24 6:37 ` Stefan Hajnoczi
2012-02-24 6:47 ` Avleen Vig
2018-01-10 21:21 ` Thomas Huth
2018-01-10 22:14 ` Avleen Vig
2018-01-12 10:50 ` Thomas Huth
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=20120223091212.GA10575@stefanha-thinkpad.localdomain \
--to=stefanha@gmail.com \
--cc=939027@bugs.launchpad.net \
--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).