Below is an example after my recent fresh install of Fedora on a new NVME SSD. This will now send the TRIM operation to the drive and report on the number of discarded bytes from each file system. This will simply show what the fstrim command will do based on the file systems that it finds configured in your /etc/fstab file. $ sudo /usr/sbin/fstrim -fstab -verbose -dry-run I’ll also leave off the quiet argument so I can determine if any errors will occur with my drive setup. For instance, I can start with the safest one, which is the dry run. Knowing these options is helpful for testing. So, now I can see that the systemd service is configured to run the trim on all supported mounted filesystems in my /etc/fstab file –fstab and print the number of discarded bytes –verbose but suppress any error messages that might occur –quiet. v, -verbose print number of discarded bytes m, -minimum the minimum extent length to discard l, -length the number of bytes to discard o, -offset the offset in bytes to start discarding from A, -fstab trim all supported mounted filesystems from /etc/fstab a, -all trim all supported mounted filesystems $ sudo /usr/sbin/fstrim -helpĭiscard unused blocks on a mounted filesystem. The –help argument to fstrim will describe these and other arguments. I do this by opening a terminal and issuing the command that the service is configured to call. I like to test first, to better understand what is happening behind the scenes. The existence and status will depend on an individual distribution basis. If you’re working on Fedora Workstation 31 and you want to begin using this feature, you can enable it very easily. Fedora introduced this into their distribution in version 30, and, although it is not enabled by default in versions 30 and 31, it is planned to be in version 32. I recently discovered that a systemd service for TRIM exists. This is the method I used most recently on my Ubuntu Linux systems until I learned about another way.
Then I created a cron job to call the command on a scheduled basis. I removed the discard option from the fstab file. This may introduce additional activity that interferes with storage performance. Using this option causes a TRIM to be initiated every time new data is written to the drive. There has recently been debate on whether this is the best method due to possible negative performance impacts. The discard option enables automatic online TRIM. The configuration is placed into the /etc/fstab file for each file system. I initially enabled this with the discard option to the mount command. If you have been using this feature on your Linux system, then you are probably familiar with the two methods described below. Free online course: RHEL Technical Overview.
0 kommentar(er)
