From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: linux-block@vger.kernel.org
Subject: recent issues with heavy delete's causing soft lockups
Date: Sat, 27 Oct 2018 12:40:03 -0600 [thread overview]
Message-ID: <2800911.LnhMzhikfW@natasha> (raw)
Hi
As of the past few months or so I've been dealing with my workstation locking
up for upwards of minutes at a time when deleting a large directory tree. I
don't recall this being a problem before.
Current setup is 3 SATA SSDs in an lvm vg. most space is allocated to an ext4
/home where my work projects live.
The main use case causing problems is deleting the "out" directory of an
android AOSP build tree. It can be upwards of 95GB in size with 240k or more
files. If I run a `rm -fr out` or `make clean` it will lock up anything
attempting to use the disk (eg: plasma, intellij, android studio, chrome, etc)
for sometimes minutes.
I have tried different block scheduler settings including none, mq-deadline,
kyber and bfq none of which seem to improve things much at all.
It may be worth noting that disk space is starting to run low, perhaps there's
some interaction going on with free space handling or ssd wear leveling...
That said, it seems to have started happening (or at least made worse) some
time around when mq was made the default and only implementation for sata.
if it helps, my system specs are:
Kernel: Debian Sid's 4.18.0-2-amd64 (4.18.10-2)
CPU: AMD FX-8320 OCed to 4.4Ghz
RAM: 32GB DDR3 1866
MB: Asus 970 Aura Pro Gaming
Storage: Kingston HyperX 3K 240G + Samsung 850 Evo 250G + SanDisk X300 500G
I'm thinking of testing with a different or older kernel, what would be the
best to test with?
Thanks for any assistance.
--
Thomas Fjellstrom
thomas@fjellstrom.ca
next reply other threads:[~2018-10-28 3:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 18:40 Thomas Fjellstrom [this message]
2018-10-27 19:20 ` recent issues with heavy delete's causing soft lockups Jens Axboe
2018-11-02 18:25 ` Thomas Fjellstrom
2018-11-02 20:32 ` Thomas Fjellstrom
2018-11-02 20:37 ` Jens Axboe
2018-11-21 21:25 ` Thomas Fjellstrom
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=2800911.LnhMzhikfW@natasha \
--to=thomas@fjellstrom.ca \
--cc=linux-block@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