From: Jason Stubbs <jasonbstubbs@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xen.org
Subject: Re: PROBLEM: Possible race between xen, md, dm and/or xfs
Date: Tue, 12 Jun 2012 22:11:37 +1000 [thread overview]
Message-ID: <4FD731F9.8070509@gmail.com> (raw)
In-Reply-To: <20120612035737.GL22848@dastard>
On 2012-6-12 13:57 , Dave Chinner wrote:
> Nothing
> wrong with MD, LVM, or XFS. The problem is either that EBS never
> completed the IO, or Xen swallowed it and it never made to it to the
> guest OS. Either way, it does not appear to be a problem in the
> higher levels of the linux storage stack.
Thanks Dave for looking into this.
I'll be sure to give Amazon ample opportunity to diagnose things from
there side should the issue occur again and hopefully there won't be
any more people reporting extraneous issues.
--
Regards,
Jason Stubbs
next prev parent reply other threads:[~2012-06-12 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 5:45 PROBLEM: Possible race between xen, md, dm and/or xfs Jason Stubbs
2012-06-12 3:57 ` Dave Chinner
2012-06-12 12:11 ` Jason Stubbs [this message]
2012-06-14 0:18 ` Matt Wilson
2012-06-14 0:57 ` Jason Stubbs
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=4FD731F9.8070509@gmail.com \
--to=jasonbstubbs@gmail.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xen.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