> I don't have any SSD in my systems. However, doing a bit of reading on "trim" it seems it addresses a need when files are being created/deleted/modified on a system. Since that isn't happening on a RO file system it seems to me to >make little sense to enable/use "trim". My goal is trimming a file system which need to be trimmed but not modified , i guess it works but i'm not *sure* ... (because all that trim need is a file system to examine which blocks of it is in use and a drive to send commands)
>If you can afford to leave enough free un-partitioned space on the SSD, then you don't need discard or fstrim as the un-partitioned space acts as extra over-provisioning. Have a look at this blog post[1] by Kent Smith from LSI (they make >the SandForce flash controller on Intel SSD's) and the comments on it, it was very informative (for me at least). Over provisioning has different purpose than trim; by over provisioning you make sure that SSD don't need to move data around and do unnecessary garbage collection (which increases SSD wear) to free some space as its scratch book but with trim you notify the SSD that which pages are not effectively in use Thanks
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
