From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Marko Huttunen <marko@codito.se>
Subject: Re: XFS getting EAGAIN from block device
Date: Wed, 08 Jun 2011 10:11:13 +0100 [thread overview]
Message-ID: <4DEF3CB1.20900@redhat.com> (raw)
In-Reply-To: <BANLkTinc-zSEY5uQ-8i__KzWPp24Q-yB+w@mail.gmail.com>
On 06/07/2011 09:44 PM, Marko Huttunen wrote:
> HW specs:
> The XFS partition is run on a HW Raid on 2 x 1TB WD Black Caviar. Motherboard is
> an ASUS Sabertooth P67 with Intel Sandy Bridge i5-2500K CPU @ 3.30GHz.
As Mike said, it sounds like something further down the stack. You don't mention
what sort of array this is (i.e. which hardware RAID driver it's using, whether
it presents as a SCSI device etc.).
Depending on the answer to that question your next steps might involve enabling
debug in that driver, turning up the generic SCSI logging level or making use of
blktrace to try to understand where the I/O is going (or rather, where it isn't
going ;).
Regards,
Bryn.
next prev parent reply other threads:[~2011-06-08 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 20:44 XFS getting EAGAIN from block device Marko Huttunen
2011-06-07 21:47 ` Mike Snitzer
2011-06-08 9:11 ` Bryn M. Reeves [this message]
2011-06-09 15:42 ` Marko Huttunen
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=4DEF3CB1.20900@redhat.com \
--to=bmr@redhat.com \
--cc=dm-devel@redhat.com \
--cc=marko@codito.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.