From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd
Date: Tue, 14 Nov 2023 08:22:03 +0000 [thread overview]
Message-ID: <bug-217965-13602-Nv8wItrWv8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217965-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217965
--- Comment #22 from Eyal Lebedinsky (bugzilla@eyal.emu.id.au) ---
I now ran a test on 6.4.15. I copied a segment of the tree I have issues with.
7.2GB in 77,972 files.
It took just over 9 minutes to sync the drain the dirty cache, and the array
run like this
(I am watching the kB_wrtn/s column):
Device tps kB_read/s kB_wrtn/s kB_dscd/s
kB_read kB_wrtn kB_dscd
18:15:01 md127 423.00 4.00 7001.20 0.00
40 70012 0
18:15:11 md127 112.30 14.80 9689.60 0.00
148 96896 0
18:15:21 md127 28.70 3.60 964.80 0.00
36 9648 0
18:15:31 md127 321.90 4.00 1340.40 0.00
40 13404 0
18:15:41 md127 18.20 0.00 123.20 0.00
0 1232 0
18:15:51 md127 26.80 10.00 2062.00 0.00
100 20620 0
18:16:01 md127 2.60 0.00 56.40 0.00
0 564 0
18:16:11 md127 2.80 0.00 82.40 0.00
0 824 0
18:16:21 md127 6.10 0.00 150.80 0.00
0 1508 0
18:16:31 md127 86.00 16.80 4978.00 0.00
168 49780 0
18:16:41 md127 48.90 10.80 4505.60 0.00
108 45056 0
18:16:51 md127 36.10 6.80 1498.00 0.00
68 14980 0
18:17:01 md127 3.20 0.40 64.40 0.00
4 644 0
18:17:11 md127 3.40 0.80 84.80 0.00
8 848 0
18:17:21 md127 3.70 0.80 283.60 0.00
8 2836 0
18:17:31 md127 32.90 6.00 1950.00 0.00
60 19500 0
18:17:41 md127 907.50 24.00 15638.40 0.00
240 156384 0
18:17:51 md127 698.00 9.60 10476.40 0.00
96 104764 0
18:18:01 md127 146.80 0.40 4796.00 0.00
4 47960 0
18:18:11 md127 163.00 0.80 1328.80 0.00
8 13288 0
18:18:21 md127 149.50 1.20 1140.00 0.00
12 11400 0
18:18:31 md127 46.50 1.60 545.20 0.00
16 5452 0
18:18:41 md127 335.90 14.40 9770.00 0.00
144 97700 0
18:18:51 md127 119.90 4.40 3868.80 0.00
44 38688 0
18:19:01 md127 315.70 25.60 11422.80 0.00
256 114228 0
18:19:11 md127 285.80 1.20 4142.40 0.00
12 41424 0
18:19:21 md127 239.00 4.40 3888.00 0.00
44 38880 0
18:19:31 md127 116.30 1.20 1752.80 0.00
12 17528 0
18:19:41 md127 166.60 8.00 8886.00 0.00
80 88860 0
18:19:51 md127 357.20 5.60 6146.80 0.00
56 61468 0
18:20:01 md127 118.10 1.20 1670.40 0.00
12 16704 0
18:20:11 md127 66.00 6.40 802.80 0.00
64 8028 0
18:20:21 md127 139.40 4.40 1641.20 0.00
44 16412 0
18:20:31 md127 44.40 2.40 632.40 0.00
24 6324 0
18:20:41 md127 183.50 13.60 4048.40 0.00
136 40484 0
18:20:51 md127 114.40 28.40 8346.40 0.00
284 83464 0
18:21:01 md127 152.20 27.20 15576.00 0.00
272 155760 0
18:21:11 md127 75.30 1.60 1146.40 0.00
16 11464 0
18:21:21 md127 236.20 18.40 13491.20 0.00
184 134912 0
18:21:31 md127 226.70 3.60 3237.60 0.00
36 32376 0
18:21:41 md127 152.70 4.00 2048.00 0.00
40 20480 0
18:21:51 md127 92.10 7.60 1907.20 0.00
76 19072 0
18:22:01 md127 142.50 8.00 1921.60 0.00
80 19216 0
18:22:11 md127 137.30 5.60 2307.60 0.00
56 23076 0
18:22:21 md127 124.10 6.00 1511.20 0.00
60 15112 0
18:22:31 md127 105.90 4.00 1888.80 0.00
40 18888 0
18:22:41 md127 166.30 2.00 2073.20 0.00
20 20732 0
18:22:51 md127 649.90 6.80 10615.20 0.00
68 106152 0
18:23:01 md127 1253.70 8.80 175698.40 0.00
88 1756984 0
18:23:11 md127 88.40 2.00 66840.40 0.00
20 668404 0
18:23:21 md127 0.00 0.00 0.00 0.00
0 0 0
Is writing at a few MB/s reasonable for an array with disks that can top
200MB/s?
Note the burst at the end when a significant chunk of the data was written out.
Now running on 6.5.10 I see a very different story:
Device tps kB_read/s kB_wrtn/s kB_dscd/s
kB_read kB_wrtn kB_dscd
18:45:53 md127 2.60 0.00 10.40 0.00
0 104 0
18:46:03 md127 5.40 0.00 21.60 0.00
0 216 0
18:46:13 md127 5.40 0.00 21.60 0.00
0 216 0
18:46:23 md127 5.30 0.00 21.60 0.00
0 216 0
18:46:33 md127 5.20 0.00 20.80 0.00
0 208 0
18:46:43 md127 5.30 0.00 23.60 0.00
0 236 0
18:46:53 md127 5.10 0.00 44.00 0.00
0 440 0
18:47:03 md127 2.70 0.00 21.60 0.00
0 216 0
18:47:13 md127 5.30 0.00 26.80 0.00
0 268 0
18:47:23 md127 5.40 0.00 25.20 0.00
0 252 0
18:47:33 md127 5.20 0.00 21.60 0.00
0 216 0
18:47:43 md127 5.30 0.00 21.20 0.00
0 212 0
18:47:53 md127 5.30 0.00 22.40 0.00
0 224 0
18:48:03 md127 5.40 0.00 24.00 0.00
0 240 0
18:48:13 md127 2.60 0.00 11.20 0.00
0 112 0
18:48:23 md127 5.30 0.00 22.40 0.00
0 224 0
18:48:33 md127 5.30 0.00 23.20 0.00
0 232 0
18:48:43 md127 5.20 0.00 24.40 0.00
0 244 0
18:48:53 md127 5.30 0.00 22.00 0.00
0 220 0
18:49:03 md127 6.20 3.60 23.20 0.00
36 232 0
18:49:13 md127 3.40 0.00 20.80 0.00
0 208 0
18:49:23 md127 5.20 0.00 20.80 0.00
0 208 0
18:49:33 md127 5.30 0.00 22.00 0.00
0 220 0
18:49:43 md127 5.30 0.00 21.60 0.00
0 216 0
18:49:53 md127 5.20 0.00 33.20 0.00
0 332 0
I expect this to take much longer to complete, possibly hours (20% drained in
the last 30m).
In both cases the flusher thread was running at 100%CPU.
I do have the full logs though.
HTH
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-11-14 8:22 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 8:10 [Bug 217965] New: ext4(?) regression since 6.5.0 on sata hdd bugzilla-daemon
2023-10-02 8:52 ` [Bug 217965] " bugzilla-daemon
2023-10-02 8:56 ` bugzilla-daemon
2023-10-02 8:57 ` bugzilla-daemon
2023-10-02 15:22 ` bugzilla-daemon
2023-10-02 15:55 ` bugzilla-daemon
2023-10-03 6:50 ` bugzilla-daemon
2023-10-03 6:57 ` bugzilla-daemon
2023-10-03 11:04 ` bugzilla-daemon
2023-10-03 13:42 ` bugzilla-daemon
2023-10-03 14:23 ` bugzilla-daemon
2023-10-04 12:44 ` bugzilla-daemon
2023-10-04 17:23 ` bugzilla-daemon
2023-10-11 7:53 ` bugzilla-daemon
2023-10-11 16:07 ` bugzilla-daemon
2023-10-11 22:23 ` bugzilla-daemon
2023-10-17 10:45 ` bugzilla-daemon
2023-10-17 10:52 ` bugzilla-daemon
2023-10-20 10:24 ` bugzilla-daemon
2023-10-21 10:07 ` bugzilla-daemon
2023-11-13 22:46 ` bugzilla-daemon
2023-11-14 5:55 ` bugzilla-daemon
2023-11-14 6:47 ` bugzilla-daemon
2023-11-14 8:22 ` bugzilla-daemon [this message]
2023-11-14 10:29 ` bugzilla-daemon
2023-11-15 4:06 ` bugzilla-daemon
2023-11-15 17:27 ` bugzilla-daemon
2023-11-15 22:39 ` bugzilla-daemon
2023-11-16 3:15 ` bugzilla-daemon
2023-11-16 4:05 ` bugzilla-daemon
2023-11-16 4:31 ` bugzilla-daemon
2023-11-16 4:33 ` bugzilla-daemon
2023-11-16 19:33 ` bugzilla-daemon
2023-11-17 0:01 ` bugzilla-daemon
2023-11-17 0:44 ` bugzilla-daemon
2023-11-17 1:39 ` bugzilla-daemon
2023-11-17 1:40 ` bugzilla-daemon
2023-11-17 15:39 ` bugzilla-daemon
2023-11-17 23:52 ` bugzilla-daemon
2023-11-17 23:53 ` bugzilla-daemon
2023-11-17 23:57 ` bugzilla-daemon
2023-11-18 12:10 ` bugzilla-daemon
2023-11-18 13:17 ` bugzilla-daemon
2023-11-20 6:11 ` bugzilla-daemon
2023-11-20 8:48 ` bugzilla-daemon
2023-11-27 17:31 ` bugzilla-daemon
2023-12-03 7:33 ` bugzilla-daemon
2023-12-15 11:27 ` bugzilla-daemon
2023-12-23 0:56 ` bugzilla-daemon
2023-12-23 1:48 ` bugzilla-daemon
2023-12-23 12:46 ` bugzilla-daemon
2023-12-23 14:22 ` bugzilla-daemon
2023-12-23 15:47 ` bugzilla-daemon
2023-12-29 20:35 ` bugzilla-daemon
2023-12-29 20:51 ` bugzilla-daemon
2023-12-29 21:05 ` bugzilla-daemon
2023-12-29 22:11 ` bugzilla-daemon
2023-12-29 22:13 ` bugzilla-daemon
2023-12-29 23:07 ` bugzilla-daemon
2023-12-29 23:22 ` bugzilla-daemon
2024-01-02 4:44 ` bugzilla-daemon
2024-01-02 6:44 ` bugzilla-daemon
2024-01-04 5:38 ` bugzilla-daemon
2024-01-04 22:20 ` bugzilla-daemon
2024-01-06 2:11 ` bugzilla-daemon
2024-01-06 3:18 ` bugzilla-daemon
2024-01-07 2:56 ` bugzilla-daemon
2024-02-07 11:44 ` bugzilla-daemon
2024-03-12 20:27 ` bugzilla-daemon
2024-03-17 11:58 ` bugzilla-daemon
2024-03-18 4:45 ` bugzilla-daemon
2024-03-20 6:46 ` bugzilla-daemon
2024-03-23 8:53 ` bugzilla-daemon
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-217965-13602-Nv8wItrWv8@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 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.