From: Hannes Reinecke <hare@suse.de>
To: Christian May <cmay@linux.vnet.ibm.com>
Cc: dm-devel@redhat.com
Subject: Re: RHEL6.2: path failures during good path I/O
Date: Mon, 18 Jun 2012 13:16:28 +0200 [thread overview]
Message-ID: <4FDF0E0C.1090403@suse.de> (raw)
In-Reply-To: <4FDF0AAB.7000001@linux.vnet.ibm.com>
On 06/18/2012 01:02 PM, Christian May wrote:
> So, I've started on my RHEL6.1 system filesystem I/O against 5
> multipath devices. Each multipath device contains 4 partition - two
> of them were mounted and used for fs-I/O. The exerciser was running
> for appr. 2 hours without a single path failure message. Then I'v
> started block I/O against the other 5 multipath devices.
> Pretty soon the first path failure was reported:
>
Could be a request-queue starvation.
As you're using directio any I/O requests from the checker will be
queued onto the request queue.
If the system is fully loaded it might take some time for the
checker I/O to be actually submitted; occasionally this might be
longer than the I/O timeout of the checker.
I would switch to 'tur' checker and retest.
(Well, _actually_ I would switch to _SLES_ and retest, but I guess
that's beside the point :-)
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2012-06-18 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 11:02 RHEL6.2: path failures during good path I/O Christian May
2012-06-13 13:16 ` Mike Snitzer
2012-06-14 19:15 ` Christian May
2012-06-14 21:19 ` Mike Snitzer
2012-06-18 10:03 ` Christian May
2012-06-18 11:02 ` Christian May
2012-06-18 11:16 ` Hannes Reinecke [this message]
[not found] <4FD8AC55.3050909@linux.vnet.ibm.com>
2012-06-13 15:41 ` Christian May
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=4FDF0E0C.1090403@suse.de \
--to=hare@suse.de \
--cc=cmay@linux.vnet.ibm.com \
--cc=dm-devel@redhat.com \
/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