From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Chris Mason <clm@fb.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
bugzilla-daemon@bugzilla.kernel.org,
bugzilla.kernel.org@plan9.de, linux-btrfs@vger.kernel.org,
linux-mm@kvack.org, Jan Kara <jack@suse.cz>
Subject: Re: [Bug 199931] New: systemd/rtorrent file data corruption when using echo 3 >/proc/sys/vm/drop_caches
Date: Wed, 6 Jun 2018 10:45:59 +0200 [thread overview]
Message-ID: <20180606084559.GD32433@dhcp22.suse.cz> (raw)
In-Reply-To: <20180605130329.f7069e01c5faacc08a10996c@linux-foundation.org>
On Tue 05-06-18 13:03:29, Andrew Morton wrote:
[...]
> > As for why we would do something silly as dropping the caches every hour (in a
> > cronjob), we started doing this recently because after kernel 4.4, we got
> > frequent OOM kills despite having gigabytes of available memory (e.g. 12GB in
> > use, 20GB page cache and 16GB empty swap and bang, mysql gets killed). We found
> > that that the debian 4.9 kernel is unusable, and 4.14 works, *iff* we use the
> > above as an hourly cron job, so we did that, and afterwards run into
> > rtorrent/journald corruption issues. Without the echo in place, mysql usually
> > gets oom-killed after a few days of uptime.
Do you have any oom reports to share?
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2018-06-06 8:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199931-27@https.bugzilla.kernel.org/>
2018-06-05 20:03 ` [Bug 199931] New: systemd/rtorrent file data corruption when using echo 3 >/proc/sys/vm/drop_caches Andrew Morton
2018-06-05 21:22 ` Tetsuo Handa
2018-06-05 21:38 ` Andrew Morton
2018-06-05 21:52 ` james harvey
2018-06-06 19:06 ` Marc Lehmann
2018-06-06 20:33 ` james harvey
2018-06-08 7:18 ` Duncan
2018-06-06 0:18 ` Chris Mason
2018-06-06 13:38 ` Liu Bo
2018-06-06 13:44 ` Chris Mason
2018-06-06 13:55 ` Liu Bo
2018-06-06 8:45 ` Michal Hocko [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=20180606084559.GD32433@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=bugzilla.kernel.org@plan9.de \
--cc=clm@fb.com \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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).