From: Dave Jones <davej@codemonkey.org.uk>
To: Dai Xiang <xiangx.dai@intel.com>
Cc: trinity@vger.kernel.org
Subject: Re: test processes are not all killed
Date: Wed, 2 Aug 2017 08:37:35 -0400 [thread overview]
Message-ID: <20170802123735.dmkice7c5slkpeqp@codemonkey.org.uk> (raw)
In-Reply-To: <20170802030921.mwhtygus3oambllj@linux>
On Wed, Aug 02, 2017 at 11:09:21AM +0800, Dai Xiang wrote:
> root@local ~# cat /proc/30504/stack
> [<ffffffff8122b5ac>] wb_wait_for_completion+0x5c/0x90
> [<ffffffff8122ed26>] sync_inodes_sb+0x96/0x200
> [<ffffffff81235135>] sync_inodes_one_sb+0x15/0x20
> [<ffffffff81204913>] iterate_supers+0xc3/0x120
> [<ffffffff81235455>] sys_sync+0x35/0x90
> [<ffffffff818fd39e>] tracesys_phase2+0x84/0x89
> [<ffffffffffffffff>] 0xffffffffffffffff
Ah. You might just have a *lot* of dirty pages to write out.
Does iotop show that journald is writing ?
If IO is progressing, it's not a bug. If it's completely idle, and we're
still stuck here, that's a kernel bug.
Unless you're particularly focussed on stressing filesystems, you might
want to skip the sync related syscalls (fsync,fdatasync,sync,syncfs)
Dave
next prev parent reply other threads:[~2017-08-02 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 9:38 test processes are not all killed Dai Xiang
2017-08-01 15:38 ` Dave Jones
2017-08-02 3:09 ` Dai Xiang
2017-08-02 12:37 ` Dave Jones [this message]
2017-08-03 3:17 ` Dai Xiang
2017-08-03 3:22 ` Dave Jones
2017-08-02 14:57 ` Tommi Rantala
2017-08-02 16:41 ` Dave Jones
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=20170802123735.dmkice7c5slkpeqp@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=trinity@vger.kernel.org \
--cc=xiangx.dai@intel.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).