Sort of the same question that Jason L has.
I'd rather not use DKMS, so I have these packages installed:
[root@primus:~]$ dpkg-query -l | grep -i zfs
ii libzfs4linux 2.2.2-0ubuntu9.2
amd64 OpeZFS filesystem library for Linux - general support
ii libzpool5linux 2.2.2-0ubuntu9.2
amd64 OpeZFS pool library for Linux
ii zfs-zed 2.2.2-0ubuntu9.2
amd64 OpeZFS Event Daemon
ii zfsutils-linux 2.2.2-0ubuntu9.2
amd64 command-line tools to manage OpenZFS filesystems
And the problem remains:
[root@primus:~]$ ps auxf | grep D\<
root 781 0.0 0.0 0 0 ? D< 17:54 0:00 \_
[vdev_autotrim]
root 4808 0.0 0.0 9524 2224 pts/0 S+ 17:55 0:00
\_ grep --color=auto D<
Will this be fixed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2057693
Title:
Activating autotrim results in high load average due to
uninterruptible threads
Status in Native ZFS for Linux:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Status in zfs-linux source package in Oracular:
Fix Released
Status in zfs-linux source package in Plucky:
Fix Released
Bug description:
SRU Justification
[Impact]
* High load averages when activating autotrim. Logs included below SRU
justification
[Fix]
* Cherry-pick a0aa7a2ee3b5: "Autotrim High Load Average Fix"
[Test Plan]
* Compile tested
* Run through autopkgtest regression tests
[Regression potential]
* Changes isolated, minimal regression risk. Changes already in
upstream ZFS
When activating the autotrim feature on any ZFS version starting from
2.2.0 this will lead to a permanent increase of the load average (as
diplayed in top) due to an uninterruptible vdev_autotrim thread for
each vdev capable of TRIM.
This issue has been reported
(https://github.com/openzfs/zfs/issues/15453) as well as fixed
(https://github.com/openzfs/zfs/pull/15781) upstream but the fix is
not yet backported to Ubuntu.
Since this bug was introduced with version 2.2.0 both mantic as well
as noble are affected.
How to reproduce:
1. Create a pool with at least one TRIM-capable device
2. run "zpool set autotrim=on <pool>"
3. watch the output of "top" or "runtime" and see how the load average
increases permanently even when the system is idle by one per vdev
4. running "ps aux | grep -w D" will show the broken threads:
[root@test ~]# ps aux | grep -w D\<
root 7193 0.0 0.0 0 0 ? D< 13:07 0:00
[vdev_autotrim]
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2057693/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
