From: Dave Chinner <david@fromorbit.com>
To: mikhail <mikhail.v.gavrilov@gmail.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: freezing system for several second on high I/O [kernel 4.15]
Date: Wed, 31 Jan 2018 13:22:09 +1100 [thread overview]
Message-ID: <20180131022209.lmhespbauhqtqrxg@destitution> (raw)
In-Reply-To: <1517337604.9211.13.camel@gmail.com>
On Tue, Jan 30, 2018 at 11:40:04PM +0500, mikhail wrote:
> Hi.
>
> I launched several application which highly use I/O on start and it
> caused freezing system for several second.
>
> All traces lead to xfs.
>
> Whether there is a useful info in trace or just it means that disk is slow?
Could be a disk that is slow, or could be many other
things. More information required:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
....
> [ 369.301111] disk_cache:0 D12928 5241 5081 0x00000000
Your "disk_cache" process is walking the inobt during inode
allocation:
> [ 369.301118] Call Trace:
> [ 369.301124] __schedule+0x2dc/0xba0
> [ 369.301133] ? wait_for_completion+0x10e/0x1a0
> [ 369.301137] schedule+0x33/0x90
> [ 369.301140] schedule_timeout+0x25a/0x5b0
> [ 369.301146] ? mark_held_locks+0x5f/0x90
> [ 369.301150] ? _raw_spin_unlock_irq+0x2c/0x40
> [ 369.301153] ? wait_for_completion+0x10e/0x1a0
> [ 369.301157] ? trace_hardirqs_on_caller+0xf4/0x190
> [ 369.301162] ? wait_for_completion+0x10e/0x1a0
> [ 369.301166] wait_for_completion+0x136/0x1a0
> [ 369.301172] ? wake_up_q+0x80/0x80
> [ 369.301203] ? _xfs_buf_read+0x23/0x30 [xfs]
> [ 369.301232] xfs_buf_submit_wait+0xb2/0x530 [xfs]
> [ 369.301262] _xfs_buf_read+0x23/0x30 [xfs]
> [ 369.301290] xfs_buf_read_map+0x14b/0x300 [xfs]
> [ 369.301324] ? xfs_trans_read_buf_map+0xc4/0x5d0 [xfs]
> [ 369.301360] xfs_trans_read_buf_map+0xc4/0x5d0 [xfs]
> [ 369.301390] xfs_btree_read_buf_block.constprop.36+0x72/0xc0 [xfs]
> [ 369.301423] xfs_btree_lookup_get_block+0x88/0x180 [xfs]
> [ 369.301454] xfs_btree_lookup+0xcd/0x410 [xfs]
> [ 369.301462] ? rcu_read_lock_sched_held+0x79/0x80
> [ 369.301495] ? kmem_zone_alloc+0x6c/0xf0 [xfs]
> [ 369.301530] xfs_dialloc_ag_update_inobt+0x49/0x120 [xfs]
> [ 369.301557] ? xfs_inobt_init_cursor+0x3e/0xe0 [xfs]
> [ 369.301588] xfs_dialloc_ag+0x17c/0x260 [xfs]
> [ 369.301616] ? xfs_dialloc+0x236/0x270 [xfs]
> [ 369.301652] xfs_dialloc+0x59/0x270 [xfs]
> [ 369.301718] xfs_ialloc+0x6a/0x520 [xfs]
> [ 369.301724] ? find_held_lock+0x3c/0xb0
> [ 369.301757] xfs_dir_ialloc+0x67/0x210 [xfs]
> [ 369.301792] xfs_create+0x514/0x840 [xfs]
> [ 369.301833] xfs_generic_create+0x1fa/0x2d0 [xfs]
> [ 369.301865] xfs_vn_mknod+0x14/0x20 [xfs]
> [ 369.301889] xfs_vn_mkdir+0x16/0x20 [xfs]
> [ 369.301893] vfs_mkdir+0x10c/0x1d0
> [ 369.301900] SyS_mkdir+0x7e/0xf0
> [ 369.301909] entry_SYSCALL_64_fastpath+0x1f/0x96
And everything else is backed up behind it trying to allocate
inodes. There could be many, many reasons for that, and that's why
we need more information to begin to isolate the cause.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-01-31 2:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 18:40 mikhail
2018-01-31 2:22 ` Dave Chinner [this message]
2018-02-05 3:25 ` mikhail
2018-02-06 3:47 ` mikhail
2018-02-06 6:08 ` Dave Chinner
2018-02-06 7:12 ` Mikhail Gavrilov
2018-02-07 3:40 ` mikhail
2018-02-07 6:55 ` Dave Chinner
2018-02-10 9:34 ` mikhail
2018-02-10 9:35 ` mikhail
2018-02-11 22:56 ` Dave Chinner
2018-02-14 21:27 ` mikhail
2018-02-14 21:52 ` Dave Chinner
2018-02-15 3:40 ` mikhail
2018-02-15 3:42 ` mikhail
2018-02-15 3:46 ` Matthew Wilcox
2018-02-15 5:44 ` Dave Chinner
2018-02-15 19:02 ` Mikhail Gavrilov
2018-02-15 21:48 ` Dave Chinner
2018-02-18 14:02 ` Mikhail Gavrilov
2018-02-19 5:02 ` Dave Chinner
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=20180131022209.lmhespbauhqtqrxg@destitution \
--to=david@fromorbit.com \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.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