On Wed, Jan 12, 2011 at 12:33 PM, Johannes Nohl
2011/1/12 Greg KH
: On Wed, Jan 12, 2011 at 05:29:58PM +0100, Johannes Nohl wrote:
I'd like to ask for feedback. How do you treat your SSD running openSUSE 11.3?
Like a normal disk, not worrying about any TRIM crud or anything else like that. You should not have to ever send those types of commands to the disk unless you feel like potentially causing problems :)
Great, but why does http://en.opensuse.org/SDB:SSD_discard_%28trim%29_support suggest to use a tool like wiper.sh then? I would prefer to not interact with the disk by intention at all.
It's a wiki. Anyone can advise anything. In this case it was me (Greg F, not Greg k-h) I still think its a good idea, even if Greg k-h doesn't.
good luck,
Usually "good luck" is going together with "as I told you before" :)
Hm. I can't estimate the risk of such disk related stuff... So I will wait until the disk really slows down.
The danger is that wiper.sh / hdparm will tell the drive to wipe the wrong sectors. Always possible, but I have not seen any error reports of that happening at all. The only way it could in my mind is if wiper.sh ignores a kernel translation layer. ie. the kernel has at least 3 translations it handles: - normal disk partition access (just an offset is needed for this) - translated via LVM (more complex) - translated via mdraid (very complex) In theory wiper.sh is aware of those and either explicitly supports various configurations of those or it explicitly does NOT. If one is not handled correctly, but wiper.sh thinks it is, then it could map the logical sector ranges to the wrong physical sector ranges and thus cause the wrong sectors to be wiped. Again, I've seen zero reports of that on opensuse or otherwise. (I have not scoured the web looking for reports, but I do pay attention to the issue.)
Thanks
Greg F -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org