From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 203247] jbd2 gets stuck at jbd2_journal_commit_transaction frequently
Date: Mon, 15 Apr 2019 21:09:49 +0000 [thread overview]
Message-ID: <bug-203247-13602-N2POZJJl9p@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203247-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203247
Theodore Tso (tytso@mit.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #11 from Theodore Tso (tytso@mit.edu) ---
Looking at your iostat -x output, /dev/sda is completely utilized:
Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s
sda 0.00 1154.00 47.00 836.00 864.00 10076.00
avgrq-sz avgqu-sz await r_await w_await svctm %util
24.78 136.46 116.05 331.72 103.93 1.13 100.00
Note the 100% utilization and the average queue size of 136.46 I/O requests.
So as I said, this sounds like I/O overload. Your workload is simply issuing
more I/O than the disk can handle. Why is going to be a userspace issue.
If you don't care about stale data (e.g., belonging to deleted files, which may
have privacy issues if you care about GDPR, HIPPA, PCI, etc. mandates) you
could try mounting with the mount option "data=writeback". It could be that
updating to a newer version of the kernel (4.9.86 is quite antique, and you're
probably missing all sorts of security and otehr bug fixes) and a newer
userspace, and then setting up a new set of file systems formatted with ext4
will also help performance. Or there might be something going on with
userspace writes to /dev/sda that shouldn't be happening or which could be
optimized away.
But I don't see anything here which is a kernel bug.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2019-04-15 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 16:15 [Bug 203247] New: jbd2 gets stuck at jbd2_journal_commit_transaction frequently bugzilla-daemon
2019-04-10 16:25 ` [Bug 203247] " bugzilla-daemon
2019-04-10 16:26 ` bugzilla-daemon
2019-04-10 16:27 ` bugzilla-daemon
2019-04-10 16:50 ` bugzilla-daemon
2019-04-10 17:57 ` bugzilla-daemon
2019-04-10 18:01 ` bugzilla-daemon
2019-04-10 18:06 ` bugzilla-daemon
2019-04-10 18:21 ` bugzilla-daemon
2019-04-12 19:33 ` bugzilla-daemon
2019-04-15 17:15 ` bugzilla-daemon
2019-04-15 21:09 ` bugzilla-daemon [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=bug-203247-13602-N2POZJJl9p@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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