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: Thu, 15 Feb 2018 08:52:45 +1100 [thread overview]
Message-ID: <20180214215245.GI7000@dastard> (raw)
In-Reply-To: <1518643669.6070.21.camel@gmail.com>
On Thu, Feb 15, 2018 at 02:27:49AM +0500, mikhail wrote:
> On Mon, 2018-02-12 at 09:56 +1100, Dave Chinner wrote:
> > IOWs, this is not an XFS problem. It's exactly what I'd expect
> > to see when you try to run a very IO intensive workload on a
> > cheap SATA drive that can't keep up with what is being asked of
> > it....
> >
>
> I am understand that XFS is not culprit here. But I am worried
> about of interface freezing and various kernel messages with
> traces which leads to XFS. This is my only clue, and I do not know
> where to dig yet.
I've already told you the problem: sustained storage subsystem
overload. You can't "tune" you way around that. i.e. You need a
faster disk subsystem to maintian the load you are putting on your
system - either add more disks (e.g. RAID 0/5/6) or to move to SSDs.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
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: Thu, 15 Feb 2018 08:52:45 +1100 [thread overview]
Message-ID: <20180214215245.GI7000@dastard> (raw)
In-Reply-To: <1518643669.6070.21.camel@gmail.com>
On Thu, Feb 15, 2018 at 02:27:49AM +0500, mikhail wrote:
> On Mon, 2018-02-12 at 09:56 +1100, Dave Chinner wrote:
> > IOWs, this is not an XFS problem. It's exactly what I'd expect
> > to see when you try to run a very IO intensive workload on a
> > cheap SATA drive that can't keep up with what is being asked of
> > it....
> >
>
> I am understand that XFS is not culprit here. But I am worried
> about of interface freezing and various kernel messages with
> traces which leads to XFS. This is my only clue, and I do not know
> where to dig yet.
I've already told you the problem: sustained storage subsystem
overload. You can't "tune" you way around that. i.e. You need a
faster disk subsystem to maintian the load you are putting on your
system - either add more disks (e.g. RAID 0/5/6) or to move to SSDs.
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-02-14 21:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 18:40 freezing system for several second on high I/O [kernel 4.15] mikhail
2018-01-31 2:22 ` Dave Chinner
2018-01-31 2:22 ` Dave Chinner
2018-02-05 3:25 ` mikhail
2018-02-06 3:47 ` mikhail
2018-02-06 6:08 ` Dave Chinner
2018-02-06 6:08 ` Dave Chinner
2018-02-06 7:12 ` Mikhail Gavrilov
2018-02-06 7:12 ` Mikhail Gavrilov
2018-02-07 3:40 ` mikhail
2018-02-07 6:55 ` Dave Chinner
2018-02-07 6:55 ` Dave Chinner
2018-02-10 9:34 ` mikhail
2018-02-10 9:34 ` mikhail
2018-02-10 9:35 ` mikhail
2018-02-11 22:56 ` Dave Chinner
2018-02-11 22:56 ` Dave Chinner
2018-02-14 21:27 ` mikhail
2018-02-14 21:27 ` mikhail
2018-02-14 21:52 ` Dave Chinner [this message]
2018-02-14 21:52 ` Dave Chinner
2018-02-15 3:40 ` mikhail
2018-02-15 3:42 ` mikhail
2018-02-15 3:42 ` mikhail
2018-02-15 3:46 ` Matthew Wilcox
2018-02-15 3:46 ` Matthew Wilcox
2018-02-15 5:44 ` Dave Chinner
2018-02-15 5:44 ` Dave Chinner
2018-02-15 19:02 ` Mikhail Gavrilov
2018-02-15 19:02 ` Mikhail Gavrilov
2018-02-15 21:48 ` Dave Chinner
2018-02-15 21:48 ` Dave Chinner
2018-02-18 14:02 ` Mikhail Gavrilov
2018-02-18 14:02 ` Mikhail Gavrilov
2018-02-19 5:02 ` Dave Chinner
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=20180214215245.GI7000@dastard \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.