From: Roman Mamedov <rm@romanrm.net>
To: Michael Reinelt <michael@reinelt.co.at>
Cc: linux-raid@vger.kernel.org
Subject: Re: heavy IO on nearly idle RAID1
Date: Tue, 19 Mar 2024 23:05:46 +0500 [thread overview]
Message-ID: <20240319230546.6ff409ca@nvm> (raw)
In-Reply-To: <ae0328a65c8a8df66dee1779036a941d2efd8902.camel@reinelt.co.at>
On Tue, 19 Mar 2024 15:08:57 +0100
Michael Reinelt <michael@reinelt.co.at> wrote:
> I think I found at least a workaround: the strange behaviour disappears immediately, if I disable
> UAS, and use usb-storage for the externel USB drive.
>
> options usb-storage quirks=04e8:4001:u
>
> I am sure that UAS has been used with kernel 6.1, too, where it did not cause any issues...
>
> Ideas what is going wrong in kernel 6.6? I'd like to re-enable UAS, because UAS is about 200 MB/sec
> faster than usb-storage
I think it might be related to discard or write zeroes support on 6.6. I had
some issues enabling USB TRIM on kernel 6.6, compared to 6.1.
What do you get for "lsblk -D" on both kernels and both storage drivers on 6.6,
are there any differences?
Aside from that, trying "blktrace" was a good suggestion to figure out the
process writing or even the content of what is being written.
--
With respect,
Roman
prev parent reply other threads:[~2024-03-19 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 10:31 heavy IO on nearly idle RAID1 Michael Reinelt
2024-03-18 1:33 ` Yu Kuai
2024-03-18 5:57 ` Michael Reinelt
2024-03-19 14:08 ` Michael Reinelt
2024-03-19 17:35 ` Roger Heflin
2024-03-19 17:43 ` Michael Reinelt
2024-03-19 17:48 ` Paul Menzel
2024-03-24 11:05 ` Michael Reinelt
2024-03-19 18:05 ` Roman Mamedov [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=20240319230546.6ff409ca@nvm \
--to=rm@romanrm.net \
--cc=linux-raid@vger.kernel.org \
--cc=michael@reinelt.co.at \
/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.