From: Spelic <spelic@shiftmail.org>
To: device-mapper development <dm-devel@redhat.com>
Subject: How to reissue stuck inflight i/o
Date: Tue, 26 Nov 2013 18:54:14 +0100 [thread overview]
Message-ID: <5294E046.409@shiftmail.org> (raw)
Hello all,
we just had a case in which some I/Os were apparently stuck inflight in
an LV aka DM (visible in iostat as nonzero avgqu-sz for an dm-X device)
for a long time, such as at least 20 minutes, but all layers below it
had zero inflight I/O (MD RAID and then the disks), so DM and the above
layers were waiting endlessly.
This was with an old kernel 2.6.24-something .
I wasn't able to debug further. After 30 minutes or so it resolved by
itself without leaving anything in dmesg or anywhere else.
Is there a way to reissue inflight I/O to lower layers (such as what
happens transparently with the 5 SCSI retries after SCSI timeout) for
DM, or at least kill such I/O so that above layers receive an I/O error
and move on?
I was thinking at some dmsetup command but was not clear to me which.
What about a dmsetup suspend and then resume? I didn't think about
trying this, at that time.
Thanks
S.
next reply other threads:[~2013-11-26 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 17:54 Spelic [this message]
2013-11-27 1:23 ` How to reissue stuck inflight i/o Mikulas Patocka
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=5294E046.409@shiftmail.org \
--to=spelic@shiftmail.org \
--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 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.