SSD / filesystem / TRIM
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
(Putting Mark Lord and linux-ide in cc:)
Mark,
Thomas has tried to use wiper.sh / hdparm v9.28 to trim a SSD and it failed. See below:
This is with the openSUSE 2.6.34 kernel.
On Sun, Aug 29, 2010 at 5:32 AM, Thomas Hertweck <[email protected]> wrote:
<snip>
Quoted 28 lines
I have now installed openSUSE 11.3 on a OCZ Vertex 2E SSD. I used a standard ext4 filesystem, the mount options at the moment are "rw,noatime,acl,user_xattr". Unfortunately,
wiper.shdoesn't work at all.$>
wiper.sh--verbose --commit/dev/sdb1wiper.sh: Linux SATA SSD TRIM utility, version 2.6, by Mark Lord.wiper.sh: This tool is DANGEROUS! Please read and understandwiper.sh:/usr/share/doc/packages/hdparm/README.wiperwiper.sh: before going any further.
rootdev=/dev/sdb1
fsmode2: fsmode=read-write
/: fstype=ext4
freesize = 45338732 KB, reserved = 453387 KB
Preparing for online TRIM of free space on/dev/sdb1(ext4 mounted read-write at /).
This operation could silently destroy your data. Are you sure (y/N)? y Creating temporary file (44885345 KB)..
Syncing disks..
Beginning TRIM operations..
get_trimlist=/sbin/hdparm --fibmap WIPER_TMPFILE.13467/dev/sdb:
trimming 89770696 sectors from 1493 ranges
FAILED: Input/output error
Removing temporary file..
Syncing disks..
Aborted.No joy, obviously. So what can I do?
<snip>
Quoted 11 lines
The motherboard, by the
way, is an Asus P6X58D-E, the SSD is attached to one of the 3GB/s SATA ports (Intel chip). There's also a 6GB/s SATA port (Marvell chip) on the board, but I couldn't find Linux support for that (that's why I haven't used this port).Well,... See above.
Regards,
Thomas
Mark, any thoughts why it didn't work. Have you added anything relevant to hdparm since v.9.28 that would help?
Greg
Quoted 3 lines · Greg Freemyer
Mark, any thoughts why it didn't work. Have you added anything relevant to hdparm since v.9.28 that would help?
It probably failed because it couldn't cope with the long trimlist that was fed to it. That's the drive's fault, really.
But the latest hdparm/wiper from sourceforge should fare better, as it now defaults to assuming the SSD cannot handle long trim lists.
Cheers
Quoted 6 lines · Mark Lord
Quoted 3 lines · Greg Freemyer
Mark, any thoughts why it didn't work. Have you added anything relevant to hdparm since v.9.28 that would help?
Quoted 7 lines
It probably failed because it couldn't cope with the long trimlist that was fed to it. That's the drive's fault, really.
But the latest hdparm/wiper from sourceforge should fare better, as it now defaults to assuming the SSD cannot handle long trim lists.
Cheers
Mark,
Does hdparm v.9.30 have any known kernel dependencies that would keep it from working with 2.6.31?
Or any other known issues that would argue against opensuse pushing it out as a software update for 11.2 and 11.3?
Or at least putting it in a OBS repo so people using wiper.sh/hdparm can use the latest if they load if from the repo..
Thanks
Greg
Signature · 10 lines
Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer CNN/TruTV Aired Forensic Imaging Demo - http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com
Quoted 9 lines · Greg Freemyer
Does hdparm v.9.30 have any known kernel dependencies that would keep it from working with 2.6.31?
Or any other known issues that would argue against opensuse pushing it out as a software update for 11.2 and 11.3?
Or at least putting it in a OBS repo so people using wiper.sh/hdparm can use the latest if they load if from the repo..
No issues that I know about.
My own opinion, is that _anyone_ using hdparm should be using v9.30.
Cheers
A message that is not in the archive (sent off-list or not yet received): 4C7CFDFD.5000902-R6A+fiHC8nRWk0Htik3J/[email protected]
Quoted 8 lines · Mark Lord
Quoted 7 lines · Greg Freemyer
Does hdparm v.9.30 have any known kernel dependencies that would keep it from working with 2.6.31?
Or any other known issues that would argue against opensuse pushing it out as a software update for 11.2 and 11.3?
Quoted 8 lines
Quoted 2 lines
Or at least putting it in a OBS repo so people using wiper.sh/hdparm can use the latest if they load if from the repo..
No issues that I know about.
My own opinion, is that _anyone_ using hdparm should be using v9.30.Cheers
Mark, Thanks
Thomas, I opened a bugzilla about it:
https://bugzilla.novell.com/show_bug.cgi?id=635920
I hope you'll add yourself as a cc: and test hdparm v9.30 if and when it is available for test.
Thanks
Greg