From: simd@vfemail.net
To: <linux-kernel@vger.kernel.org>, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Cannot change RAID array check speed
Date: Mon, 16 Feb 2026 10:14:52 -0500 [thread overview]
Message-ID: <20260216101452.2f28a76b@Core-Ultra-2-x20> (raw)
In-Reply-To: <CALtW_ahB7MUVgRuf=3itf-XbYW_nuEyj_p2-BGEk71mkrVg6FA@mail.gmail.com>
It worked with LK 6.9 on Devuan (Debian Stretch) ASCII.
I upgraded the system, both HW and SW, to Daedalus and I had to go with a
newer kernel to use the newer Intel iGPU. I'm now on Devuan (Debian
Bookworm) Daedalus.
I used to change this value all the time to get the check done faster or
to slow it down because I needed to access the array.
Maybe it's a distro security policy? IDK. But as I said, I used to change
it all the time. That's why there's a sync_speed_min/max, or so I thought.
Thanks,
David
PS: Accidentally sent to the user instead of to the list. Sorry.
On Mon, 16 Feb 2026 06:20:58 +0100
Dragan Milivojević <galileo@pkm-inc.com> wrote:
> When did that work?
> /sys/devices/virtual/ etc
> is readonly on 4.18, 6.12 and 6.18 (a few boxes that I have).
>
>
>
> On Mon, 16 Feb 2026 at 04:15, David Niklas <simd@vfemail.net> wrote:
> >
> > Hello,
> > I upgraded my kernel from 6.9 to 6.17. They're both the "same" custom
> > config. I tried:
> >
> > # echo 200000 > /sys/devices/virtual/block/md7/md/sync_speed
> > bash: /sys/devices/virtual/block/md7/md/sync_speed: Permission denied
> > # id
> > uid=0(root) gid=0(root) groups=0(root)
> >
> > This used to work. Any ideas as to what I could have set wrong? I
> > haven't a clue!
> >
> > Is there a security debugging tool or a log-file I could use to trace
> > this down?
> >
> > Thanks,
> > David
> >
next prev parent reply other threads:[~2026-02-16 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 3:08 Cannot change RAID array check speed David Niklas
2026-02-16 3:10 ` David Niklas
[not found] ` <CALtW_ahB7MUVgRuf=3itf-XbYW_nuEyj_p2-BGEk71mkrVg6FA@mail.gmail.com>
2026-02-16 15:14 ` simd [this message]
2026-02-16 20:01 ` David Niklas
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=20260216101452.2f28a76b@Core-Ultra-2-x20 \
--to=simd@vfemail.net \
--cc=linux-kernel@vger.kernel.org \
--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