beertje44
beertje44
Would be a nice enhanchment, running years old software makes me nervious ;) And from the looks of it the bundled mysql for docker is mysql 3.x!!!!!!!! Please fix this...
You are right, the problem seems to be with dkms. kvdo builds just fine, but after that there is a problem during the "Adding weak modules" stage: it gives depmod...
FYI: on 6.6.5 there does seem to be a race condition, it boots but then eventually dracut is unable to find the main (vdo backed) lv. 6.6.3 boots and works...
> I think you are right and your solution works for me on AlmaLinux 9.1 also, thanks for that. What I fail to understand is why this issue keeps popping...
This one liner fixed it for all my flatpak apps: `flatpak list --app --columns=application,runtime|grep org.gnome.Platform|awk -F '\t' '{print "flatpak run --command=fc-cache " $1 " -f -v /usr/share/fonts/cantarell"}'|xargs -I % echo...
For me there is a clear drop in performance on my Samsung nvme SSD. It should do sequential throughput in the range of 5GB/s+ and 800k iops in random I/O....
On the other hand: I recently converted my home storage to be encrypted: luks2 encrypted partition->lvm2 pv->lvm2 vg->vdo lvm2 lv's for root and yours truly. Luks doesn't seem to impact...
    Just some simple Kdiskmarks runs with and without vdo and with en without O_Direct. Somehow max throughput was always with O_Direct and max IOPS...
Did some more digging around: - I booted the default kernel for AlmaLinux 9.1: 5.14.0-162.23.1.el9_1.x86_64. As soon as I entered `time fstrim -v /` the system almost completely locked up....
> 2 advices : > > run fstrim in background (add "&" at the end of your command) so that it returns the PID and you can just kill >...