I've recently got a G.Skill Phoenix Pro 60GB drive ( FM-25S2S-60GBP2 ), a sandforce SF-1200 based drive. I'm interested in checking TRIM is working correctly.
* I have installed Maverick Meerkat (with all updates) on an ext4 partition. This has a kernel that includes TRIM support.
* Edited /etc/fstab to add the discard option which enables TRIM
* I have downloaded the wiper.sh 2.7 files directly from hdparm project, as wiper.sh was not included in meerkat that I could find.
To see if the kernel TRIM was working, I followed some simple steps. Everything looks fine, and I am seeing the correct output according to that guide. I read the sector and see all the zeroes 0000 0000 output.
I have run wiper.sh manually on another ext4 partition that has 10.04 installed (stock, all updates). When I boot into that it does not have a TRIM enabled kernel. So, I booted into Meekat and ran wiper.sh against that partition to 'clean it up'.
When I run it, it seems to run successfully.
$ sudo ./wiper.sh --commit /dev/sda4
wiper.sh: Linux SATA SSD TRIM utility, version 2.7, by Mark Lord.
Preparing for online TRIM of free space on /dev/sda4 (ext4 mounted read-write at /mnt/ubuntu1004).
This operation could silently destroy your data. Are you sure (y/N)? y
Creating temporary file (9251416 KB)..
Beginning TRIM operations..
trimming 18502832 sectors from 325 ranges
Removing temporary file..
There is disk activity for a little while, and so it appears to work. I've also tried the same with a patched version with -max-ranges in case the drive has a limited number of ranges it can accept in the TRIM command. The result is the same.
*when I re-run the command, it shows exactly the same output, ie trimming 18502832 sectors from 325 ranges. Does this mean it hasn't worked?
*when I use the -verbose flag and then examine one of the sectors that is reported to be going to be TRIM'ed, it still shows data in it, ie it hasn't been zeroed as in when the kernel does the TRIM.
Is the above expected operation?
Log in to post a comment.