Bug 2223570

Summary:	ostree-based distributions (Silverblue, Kinoite, etc.) can not run discard on SSD when LUKS encryption is enabled
Product:	[Fedora] Fedora	Reporter:	Garrett LeSage <glesage>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	39	CC:	anaconda-maint-list, vponcova, vslavik, vtrefny, w
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
URL:	https://github.com/fedora-silverblue/issue-tracker/issues/31
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-11-27 21:15:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Garrett LeSage 2023-07-18 10:01:54 UTC

After installing an ostree-based desktop distribution of Fedora (Silverblue, Kinoite, etc.), the computer will become slower and slower over time when IO happens, as discard is not properly enabled. The IO problems eventually become so bad that the computer can hang for minutes with no response.

It's probably an issue with the way Anaconda sets up the system. It may also be an issue with ostree deployment. (It could be both of these things.)

Reproducible: Always

Steps to Reproduce:
1. Install Silverblue on a device that needs trim 
2. Check to see if you can trim the device (fstrim -va is one method)

Actual Results:  
No discard support. Computer becomes slower and slower on every disk access, which becomes very noticeable after a few months.

Expected Results:  
Discard should happen automatically with fstrim.timer (and when run manually).

Workstation is fine. This is a problem only with ostree-based distributions (not inherent to ostree itself, but with the way they're installed).

Comment 1 Garrett LeSage 2023-07-18 10:05:41 UTC

I solved it locally with `sudo cryptsetup --allow-discards --persistent refresh /dev/mapper/luks*`

Vojtech Trefny says `rd.luks.options=discard` via Anaconda should solve it for everyone (on fresh installs).

Comment 2 Vojtech Trefny 2023-07-18 10:14:09 UTC

(In reply to Garrett LeSage from comment #1)
> Vojtech Trefny says `rd.luks.options=discard` via Anaconda should solve it
> for everyone (on fresh installs).

Note this is based on this[1] Fedora Silverblue issue, I am certainly not expert on OSTree/Silverblue and I'm open to different solution.

[1] https://github.com/fedora-silverblue/issue-tracker/issues/31

Comment 3 Fedora Release Engineering 2023-08-16 08:07:05 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 4 Aoife Moloney 2024-11-08 10:55:56 UTC

This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2024-11-27 21:15:59 UTC

Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.