linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd
Date: Sat, 18 Nov 2023 13:17:59 +0000	[thread overview]
Message-ID: <bug-217965-13602-AVoESEUTYG@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 #41 from Eyal Lebedinsky (bugzilla@eyal.emu.id.au) ---
OK, so how do I disable the stripe=640 that was automatically added?
Is there a mount option to disable it?
I would rather not futz with tune2fs.

RE kernel build: I used to often do this maybe 30 years ago, but on a
workstation, not on the server. The build I expect to be simple, but it is the
risk of a bad patch that worries me. I would rather not do that.

BTW, while you are looking at the cache issue, what are your thoughts on the
fact that the array shows (iostat -x) a very high w_await when the members are
much lower? Is it normal?

         Device            r/s     rkB/s   rrqm/s  %rrqm r_await rareq-sz    
w/s     wkB/s   wrqm/s  %wrqm w_await wareq-sz     d/s     dkB/s   drqm/s 
%drqm d_await dareq-sz     f/s f_await  aqu-sz  %util
16:04:08 md127            0.20      0.80     0.00   0.00   10.50     4.00   
9.80    739.20     0.00   0.00 1495.44    75.43    0.00      0.00     0.00  
0.00    0.00     0.00    0.00    0.00   14.66   4.51
16:04:08 sdb              2.30    187.20    44.50  95.09   30.74    81.39   
6.80    345.20    79.70  92.14   29.72    50.76    0.00      0.00     0.00  
0.00    0.00     0.00    0.60   14.33    0.28   1.26
16:04:08 sdc              1.90    138.80    32.80  94.52   16.63    73.05   
6.60    295.60    67.50  91.09   13.06    44.79    0.00      0.00     0.00  
0.00    0.00     0.00    0.60   11.33    0.12   1.05
16:04:08 sdd              2.30    194.40    46.30  95.27    3.70    84.52   
2.90    138.80    32.00  91.69    3.34    47.86    0.00      0.00     0.00  
0.00    0.00     0.00    0.60    4.67    0.02   0.54
16:04:08 sde              1.80    204.00    49.20  96.47   14.89   113.33   
4.10    302.40    71.70  94.59   13.27    73.76    0.00      0.00     0.00  
0.00    0.00     0.00    0.60    6.17    0.08   1.66
16:04:08 sdf              1.90     97.20    22.40  92.18   14.63    51.16   
4.70    212.00    48.50  91.17   19.70    45.11    0.00      0.00     0.00  
0.00    0.00     0.00    0.60   11.50    0.13   1.98
16:04:08 sdg              2.00    212.00    51.00  96.23    7.80   106.00   
4.70    279.20    65.30  93.29    8.32    59.40    0.00      0.00     0.00  
0.00    0.00     0.00    0.60    8.00    0.06   1.86
16:04:08 sdh              2.20    213.20    51.10  95.87   21.73    96.91   
4.80    315.60    74.30  93.93   27.77    65.75    0.00      0.00     0.00  
0.00    0.00     0.00    0.60   14.33    0.19   2.05

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-11-18 13:18 UTC|newest]

Thread overview: 75+ 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
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 [this message]
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
2025-08-18 13:48 ` bugzilla-daemon
2025-08-27 17:07 ` 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-AVoESEUTYG@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 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).