Am Dienstag, dem 19.03.2024 um 18:48 +0100 schrieb Paul Menzel: > As you can reproduce this, and it works with an earlier version, the > fastest way to resolve the issue is unfortunately to bisect the issue to > find the commit causing the regression. I agree, but bisecting between kernel 6.1.76 and 6.6.13 sounds like a bit of work, doesn't it? :-( As this happens on my computer that I need for work every day (and night :-), it makes it even more complicated. I could try to set up another system (hardware available, but I'd have to buy a SSD for it), but this will take some time... Am Dienstag, dem 19.03.2024 um 23:05 +0500 schrieb Roman Mamedov: > 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? I tried 6.1 and 6.6 both with UAS enabled/disabled, and I get identical results: NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO sda 0 512B 2G 0 ├─sda1 0 512B 2G 0 │ └─md0 0 512B 2G 0 └─sda2 0 512B 2G 0 └─md1 0 512B 2G 0 sdb 0 0B 0B 0 ├─sdb1 0 0B 0B 0 │ └─md0 0 512B 2G 0 └─sdb2 0 0B 0B 0 └─md1 0 512B 2G 0 sdc 0 0B 0B 0 nvme0n1 0 512B 2T 0 ├─nvme0n1p1 0 512B 2T 0 ├─nvme0n1p2 0 512B 2T 0 ├─nvme0n1p3 0 512B 2T 0 │ └─md0 0 512B 2G 0 └─nvme0n1p4 0 512B 2T 0 > Aside from that, trying "blktrace" was a good suggestion to figure out the > process writing or even the content of what is being written. I tried to understand blktrace, but failed :-) I've never worked with this tool... Can someone give me advices how to use it, and which results you are interested in? greetings, Michael -- Michael Reinelt <michael@xxxxxxxxxxxxx> Ringsiedlung 75 A-8111 Gratwein-Straßengel +43 676 3079941
