Update 4.0.0 removes emulate_tpu from Lio_tunings

dbutti
36 Posts
October 8, 2025, 8:28 amQuote from dbutti on October 8, 2025, 8:28 amGood morning; after the latest 4.0.0/4.0.1 Petasan update I started getting errors from my iSCSI initiators, because the LIO target seems not to support DISCARD/TRIM as it previously did. Upon checking, it emerged that the emulate_tpu=1 option which I used to have in the /opt/petasan/config/tuning/current/lio_tunings has disappeared.
Is this expected? Shall I add back this option manually to the config file?
Thank-you,
Good morning; after the latest 4.0.0/4.0.1 Petasan update I started getting errors from my iSCSI initiators, because the LIO target seems not to support DISCARD/TRIM as it previously did. Upon checking, it emerged that the emulate_tpu=1 option which I used to have in the /opt/petasan/config/tuning/current/lio_tunings has disappeared.
Is this expected? Shall I add back this option manually to the config file?
Thank-you,

admin
3,054 Posts
October 8, 2025, 2:30 pmQuote from admin on October 8, 2025, 2:30 pmThe flag is now per disk, you can edit each disk to enable flag. it is not in the cluster tuning as before, but you should be able to re-add it there and it will apply to all disks.
note that now you do not edit the tuning files on each node, now you edit from the UI under tuning profiles and it will apply to all nodes.
Sill it is best to configure tpu on a disk per disk rather than entire cluster.
The flag is now per disk, you can edit each disk to enable flag. it is not in the cluster tuning as before, but you should be able to re-add it there and it will apply to all disks.
note that now you do not edit the tuning files on each node, now you edit from the UI under tuning profiles and it will apply to all nodes.
Sill it is best to configure tpu on a disk per disk rather than entire cluster.

dbutti
36 Posts
October 8, 2025, 3:33 pmQuote from dbutti on October 8, 2025, 3:33 pmThank you, I have checked the settings and it seems that my LUNs have discard/trim support enabled. Still, today I got this error from a Linux initiator (oVirt). Is it just a spurious error message from the initiator? is there a safe way for me to confirm trim/discard is enabled on each target using targetcli-fb or similar on the Petasan nodes?
Thank you, I have checked the settings and it seems that my LUNs have discard/trim support enabled. Still, today I got this error from a Linux initiator (oVirt). Is it just a spurious error message from the initiator? is there a safe way for me to confirm trim/discard is enabled on each target using targetcli-fb or similar on the Petasan nodes?

admin
3,054 Posts
October 8, 2025, 7:01 pmQuote from admin on October 8, 2025, 7:01 pmwhat is the error
what is the error
Update 4.0.0 removes emulate_tpu from Lio_tunings
dbutti
36 Posts
Quote from dbutti on October 8, 2025, 8:28 amGood morning; after the latest 4.0.0/4.0.1 Petasan update I started getting errors from my iSCSI initiators, because the LIO target seems not to support DISCARD/TRIM as it previously did. Upon checking, it emerged that the emulate_tpu=1 option which I used to have in the
/opt/petasan/config/tuning/current/lio_tuningshas disappeared.Is this expected? Shall I add back this option manually to the config file?
Thank-you,
Good morning; after the latest 4.0.0/4.0.1 Petasan update I started getting errors from my iSCSI initiators, because the LIO target seems not to support DISCARD/TRIM as it previously did. Upon checking, it emerged that the emulate_tpu=1 option which I used to have in the /opt/petasan/config/tuning/current/lio_tunings has disappeared.
Is this expected? Shall I add back this option manually to the config file?
Thank-you,
admin
3,054 Posts
Quote from admin on October 8, 2025, 2:30 pmThe flag is now per disk, you can edit each disk to enable flag. it is not in the cluster tuning as before, but you should be able to re-add it there and it will apply to all disks.
note that now you do not edit the tuning files on each node, now you edit from the UI under tuning profiles and it will apply to all nodes.
Sill it is best to configure tpu on a disk per disk rather than entire cluster.
The flag is now per disk, you can edit each disk to enable flag. it is not in the cluster tuning as before, but you should be able to re-add it there and it will apply to all disks.
note that now you do not edit the tuning files on each node, now you edit from the UI under tuning profiles and it will apply to all nodes.
Sill it is best to configure tpu on a disk per disk rather than entire cluster.
dbutti
36 Posts
Quote from dbutti on October 8, 2025, 3:33 pmThank you, I have checked the settings and it seems that my LUNs have discard/trim support enabled. Still, today I got this error from a Linux initiator (oVirt). Is it just a spurious error message from the initiator? is there a safe way for me to confirm trim/discard is enabled on each target using targetcli-fb or similar on the Petasan nodes?
Thank you, I have checked the settings and it seems that my LUNs have discard/trim support enabled. Still, today I got this error from a Linux initiator (oVirt). Is it just a spurious error message from the initiator? is there a safe way for me to confirm trim/discard is enabled on each target using targetcli-fb or similar on the Petasan nodes?
admin
3,054 Posts
Quote from admin on October 8, 2025, 7:01 pmwhat is the error
what is the error