SDD fstrim

I searched the forums and google for anything similar but have not really found anything so I thought I give it a try here.

  • I changed laptop which has 12.3 on it from a hdd to an ssd
  • cloned the disc with G4L, fixed the disk by-id entry’s in fstab and grub.conf/device map
  • laptop boot time went from 1:30 to 0:35, all in all went very smooth
  • then looked into fstrim and ran that on / and /home. It returned a huge number (12323325234534 bytes have been trimmed or something like that)
  • ran yast to update as the laptop was a bit behind, total of 101 packages had to be done, this went really fast and after that turned laptop off
  • next morning turned it on an hang on “loading grub”, tried rescue dvd, nothing odd, fsck showed nothing either.
  • so again cloned disc with g4l, fixed fstab etc. and all was fine
  • did fstrim / and /home (showed the huge nbr of bytes), rebooted a few times, all was fine
  • ran yast to do the 101 packages
  • rebooted and grub got a little further now but still now UI, then rebooted the laptop so it was looping, again did not find anything weird with used rescue dvd, grub files all looked quiet normal
  • so again cloned disc with g4l, fixed fstab etc. and all was fine
  • ran yast to do the 101 packages
  • rebooted and all was fine
  • have not done fstrim on it so far and it still running perfect.

now the laptop is a hp pavilion 9700, you can’t do much in the bios so you can only assume its set to ahci
the ssd (samsung evo) is on latest firmware and does support trimming as the hdparm -I show

right now I am reluctant to do the fstrim but also not sure its the cause, just feels like fstrim at first is okay but when doing a huge update on the ssd (the 101 packages) it all goes wrong.

any idea’s thoughts would be appreciated

I found an article on using fstrim over the discard command in your fstab file here: Using fstrim to “TRIM” your SSD instead of “delete” in fstab | Ubuntu&Pogoplug howtos

Based on your experience, using fstrim is at your own risk! I add in the fstab mount command options of noatime and discard for the ext4 partition type. I can add in noatime for all partitions types and gain speed. Here are the fstab settings I use:

/dev/disk/by-id/ata-Samsung_SSD_840_Series_S14JNEAD303010R-part1 swap         swap       defaults,noatime                                 0 1
/dev/disk/by-id/ata-Samsung_SSD_840_Series_S14JNEAD303010R-part2 /            ext4       acl,user_xattr,noatime,discard,errors=remount-ro 0 1

For edits of the fstab file, have a look at my bash script here:

SYSEdit - System File Editor - Version 1.50 - Blogs - openSUSE Forums

Thank You,

Don’t let yourself get upset by all the alarming stuff out there. If you’d have to go through manual trimming, IMHO (and others’) something would be seriously wrong with linux. Again IMHO, distros should use noatime and discard as default for partitions on SSD’s, since it’s advized to do so by the kernel people.
To get back to my first line: my 6 year old 30GB SSD is still working despite of no tuning whatsoever and stressing it all the time. In fact, I have had serious issues with HDD’s but the first SSD problem has yet to appear

I’ll enable discard and see how that goes and ignore fstrim :slight_smile: thanks for the answers

Sounds good and don’t ignore noatime, usable on ANY partition type you mount from the fatab file. I would check out SystEdit, my bash file system file editor selector.

Thank You,

I have used fstrim on my Intel 330. My understanding is that it always returns the number of bytes on the partition you have run fstrim on, hence the large number. Of course the number of bytes cleaned up would be more useful, but so be it… Using fstrim periodically has not caused me any problems. Though with my SSD I have enough free space and no IO issues at all so barely remember to run fstrim.

From what you say it sounds to me like a faulty package update problem rather than the SSD. I have found from past experience that accepting all package updates can lead to boot failures. So two suggestions 1) either use fstrim but hold off making any package updates, does everything then go well? 2) clone SSD to a spare mechanical hard drive, apply all the package updates, does that also lead to the problem?