From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS hangs - possibly NFS related?
Date: Sun, 25 May 2014 22:36 +1000 [thread overview]
Message-ID: <1414589.yRqiue0P7g@quad> (raw)
In-Reply-To: <058b01cf780e$6ae065c0$40a13140$@bluemoose.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 25 May 2014 12:42:32 PM kim-btrfs@bluemoose.org.uk wrote:
> Any ideas of what I can do to help debug it...?
Looking at that output it seems that all those blocked processes are in
congestion_wait() in mm/backing-dev.c, the comments for which say:
/**
* congestion_wait - wait for a backing_dev to become uncongested
* @sync: SYNC or ASYNC IO
* @timeout: timeout in jiffies
*
* Waits for up to @timeout jiffies for a backing_dev (any backing_dev) to exit
* write congestion. If no backing_devs are congested then just wait for the
* next write to be completed.
*/
The blocked tasks are:
kswapd0
smbd (which correlates with what you've said before)
ShFolders (is this something local?)
ATA-0 (I suspect a kernel process handling that device)
Interestingly there are no calls to congestion_wait() in fs/btrfs so those
blocked tasks are blocked accessing other filesystems.
One thing that would be interesting is to see the wchan of processes blocked
in device wait state when you're in that situation.
Something like this should do it:
ps -eo pid,user,stat,wchan:30,comm | fgrep -w D
Is this system under memory pressure at the time these happen?
All the best,
Chris
- --
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEVAwUBU4HjtI1yjaOTJg85AQKPYAgAlI7elWEx0YxPqABFmS3cUVIgTskxFL6/
ha7G1wxIxeqxhx1x1cLE3oKsCAhJlrwXd6cB8e0Kmu2280fCa/N9uqdJaMq+E8ha
VU0K0D6lAd2lJP9L1XVI2hlAO8YEwuFpe5ebYk//1LERsZxkPVJSrIntVKvG8aCR
9fHLa9W7Pscn9oOyC2Nvh/z4FAAHu0/QWj/uuA8cOUX0FRyHrsqhhi3a+zHNJkOo
vB6nfd/TWJXXDTRO6Og9ozW8InvAvpuG0NNOVSVQd10xc09qLMaP98cBBhisFji/
r3RZ0GiyW4SlYjQWhfxP9eBtZlsQD8lZMGEXHPyzlHZrJzMfjQjJvw==
=h6xh
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-05-25 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 12:56 BTRFS hangs - possibly NFS related? kim-btrfs
2014-04-02 6:58 ` Duncan
2014-05-25 11:42 ` kim-btrfs
2014-05-25 12:36 ` Chris Samuel [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=1414589.yRqiue0P7g@quad \
--to=chris@csamuel.org \
--cc=linux-btrfs@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