From: Al Viro <viro@ZenIV.linux.org.uk>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: cat /proc/mdstat blocking?
Date: Fri, 5 Aug 2011 16:23:38 +0100 [thread overview]
Message-ID: <20110805152338.GU2203@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4E3BF809020000A100006CDF@gwsmtp1.uni-regensburg.de>
On Fri, Aug 05, 2011 at 02:02:49PM +0200, Ulrich Windl wrote:
> Hi,
>
> I thought that /proc/mdstat just displays the current state of the MD RAIDs, not querying them, thus never blocking. Unfortunately I could observer a "cat /proc/mdstat" hanging for several seconds when one of the RAID1 legs was unavailable and multipathd was queueing requests to the leg.
>
> Practically this makes monitoring of the other RAIDs difficult when one bad device is enough to block /proc/mdstat.
>
> Now my question: Does it work as designed (i.e. as intended), or is this not as intended?
I suspect that something is holding all_mddevs_lock too long; that, or one
of the subdrivers' spinlocks. Try to find out what it blocks on and what
holds the lock in question...
prev parent reply other threads:[~2011-08-05 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 12:02 Q: cat /proc/mdstat blocking? Ulrich Windl
2011-08-05 15:23 ` Al Viro [this message]
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=20110805152338.GU2203@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=linux-kernel@vger.kernel.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 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.