public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Truschnigg <johannes@truschnigg.info>
To: eyal@eyal.emu.id.au
Cc: linux-raid@vger.kernel.org
Subject: Re: extremely slow writes to array [now not degraded]
Date: Mon, 13 Nov 2023 11:09:32 +0100	[thread overview]
Message-ID: <ZVH13JX6q-5CsQNN@vault.lan> (raw)
In-Reply-To: <09d9848d-8ef4-488c-8719-7ad451c9e36b@eyal.emu.id.au>

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

On Mon, Nov 13, 2023 at 08:58:55PM +1100, eyal@eyal.emu.id.au wrote:
> [trimmed]
> > > [0]: https://bugzilla.kernel.org/show_bug.cgi?id=217965
> 
> Reading this bugzilla, an extra info bit. This has not changed for years (I have daily records).
> 
> $ mount|grep data1
> /dev/md127 on /data1 type ext4 (rw,noatime,stripe=640)

Yeah, afaiui, one of the theories in the bug suggests that a recently
introduced block allocation improvement made matters worse for any kind of
stride/stripe setting <> 0. So if you dial your kernel version back to before
that was made (6.4 seems to be unaffacted, iirc), you will probably regain the
performance loss you observe and reported here on list.

FWIW, I briefly played around with an artificial dataset on tmpfs-backed loop
devices configured in RAID5 where I was (re)setting the superblock-configured
stride-setting, and did not lose any data by toggling it between 0 and
<some_other_value> (256 in my case) multiple times. So I would assume that to
be a safe operation in principle ;)

-- 
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )

www:   https://johannes.truschnigg.info/
phone: +436502133337
xmpp:  johannes@truschnigg.info

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-11-13 10:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05 23:06 extremely slow writes to degraded array eyal
2023-11-07 21:14 ` Peter Grandi
2023-11-08  1:37   ` eyal
2023-11-08  5:32     ` eyal
2023-11-08 16:50       ` Peter Grandi
2023-11-09  2:59 ` extremely slow writes to array [now not degraded] eyal
2023-11-09 13:16   ` Roger Heflin
2023-11-13  0:53     ` eyal
2023-11-13  6:54       ` Johannes Truschnigg
2023-11-13  8:06         ` eyal
2023-11-13  9:20           ` Johannes Truschnigg
2023-11-13  9:36             ` eyal
2023-11-13  9:58               ` eyal
2023-11-13 10:09                 ` Johannes Truschnigg [this message]
2023-11-13 10:31                   ` eyal
2023-11-13 12:26               ` Roger Heflin

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=ZVH13JX6q-5CsQNN@vault.lan \
    --to=johannes@truschnigg.info \
    --cc=eyal@eyal.emu.id.au \
    --cc=linux-raid@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