From: Brian Foster <bfoster@redhat.com>
To: "蒋雄伟(蒋冲)" <xiongwei.jiang@alibaba-inc.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: xfs: blocked task in xfs_buf_lock
Date: Mon, 8 May 2017 09:40:38 -0400 [thread overview]
Message-ID: <20170508134037.GC29840@bfoster.bfoster> (raw)
In-Reply-To: <000201d2c548$68fc5450$3af4fcf0$@alibaba-inc.com>
On Fri, May 05, 2017 at 10:36:33AM +0800, 蒋雄伟(蒋冲) wrote:
>
>
> While testing ceph cluster and using XFS as the underlying filesystem, I've
> seen xfs blocking tasks several times.
>
> Just as https://www.mail-archive.com/search?l=stable@vger.kernel.org
> <https://www.mail-archive.com/search?l=stable@vger.kernel.org&q=subject:%22x
> fs%3A+blocked+task+in+xfs_buf_lock%22&o=newest&f=1>
> &q=subject:%22xfs%3A+blocked+task+in+xfs_buf_lock%22&o=newest&f=1
>
> And there is also another similar case
> http://oss.sgi.com/archives/xfs/2012-05/msg00307.html
>
>
>
> These two cases was reported long time ago. Is it resolved or is there any
> solution ?
>
The above looks like a very old report without any resolution. I would
suggest to report your issue based on current observations rather than
rely on it looking similar to an old report. See the following for what
information is relevant to include when reporting a problem:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
Note that the syslog and hung task output is particularly relevant here.
Brian
>
>
> Xiongwei Jiang
>
next parent reply other threads:[~2017-05-08 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000201d2c548$68fc5450$3af4fcf0$@alibaba-inc.com>
2017-05-08 13:40 ` Brian Foster [this message]
2012-05-24 11:14 xfs: blocked task in xfs_buf_lock Stefan Priebe - Profihost AG
2012-05-27 18:30 ` Stefan Priebe
2012-05-30 22:09 ` Ben Myers
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=20170508134037.GC29840@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=xiongwei.jiang@alibaba-inc.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;
as well as URLs for NNTP newsgroup(s).