From: Stan Hoeppner <stan@hardwarefreak.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: task xfssyncd blocked while raid5 was in recovery
Date: Thu, 11 Oct 2012 06:01:58 -0500 [thread overview]
Message-ID: <5076A726.3070002@hardwarefreak.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1210110810210.21297@uplift.swm.pp.se>
On 10/11/2012 1:12 AM, Mikael Abrahamsson wrote:
> On Wed, 10 Oct 2012, Stan Hoeppner wrote:
>
>> Precisely what it says. It doesn't tell you WHY it was blocked, as it
>> can't know. The fact that your md array was in recovery and having
>> problems with one of the member drives is a good reason for xfssyncd
>> to block.
>
> Doesn't he still have 3 good drives? So since sdb was failed, there
> would be no reason for sdb to cause blocking or writes to the (now
> degraded) raid5? OP said he saw write IO errors to the array (?), which
> I thought was strange.
I think the more important question is, why was the OP writing to a
filesystem on a small RAID5 array while it was doing a rebuild? My
assumption here was that the seek load due to the rebuild was what
caused xfssyncd to block. IO Load is a common cause of this particular
kernel message when it relates to XFS.
Note this msg is not an error, but informational, thus the "INFO: " tag.
This is why you have the option to turn off the message. Also note
there are many conditions that will prompt this "blocked for 120s"
kernel message, and that this message is not unique to XFS. Point of
fact, Google for "blocked for more than 120 seconds" and no results on
the first page relate to XFS.
--
Stan
next prev parent reply other threads:[~2012-10-11 11:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 3:14 task xfssyncd blocked while raid5 was in recovery GuoZhong Han
2012-10-10 11:54 ` Stan Hoeppner
2012-10-11 2:42 ` hanguozhong
2012-10-11 3:47 ` Chris Murphy
2012-10-11 11:20 ` Stan Hoeppner
2012-10-11 6:12 ` Mikael Abrahamsson
2012-10-11 11:01 ` Stan Hoeppner [this message]
2012-10-11 11:16 ` Mikael Abrahamsson
[not found] ` <201210112054336567511@meganovo.com>
2012-10-11 14:47 ` Stan Hoeppner
[not found] <CACY-59cbWX9Gu_xsfqv_p8=Q7CabWZuj=ZH2K41j4N0-o-8WLw@mail.gmail.com>
2012-10-24 3:17 ` hanguozhong
2012-10-24 5:14 ` NeilBrown
2012-10-30 2:19 ` hanguozhong
2012-10-30 4:49 ` Stan Hoeppner
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=5076A726.3070002@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).