The device takes care of determining where it will save the data based on
its knowledge of the device (areas not trimmed), but the logical view stays
the same, sectors 0 - n, otherwise they would be pretty useless. An OS is
only going to TRIM the logical areas (which may be anywhere on the device)
within the file systems it controls, to do otherwise would certainly cause
"rustleg" wrote in message news:firstname.lastname@example.org...
I wonder if anyone can put my mind at rest regarding whether SSDs
"wear-levelling" process interfere with the data stored in free
space. With BIBM you can create partitions which are hidden from the MBR.
For example I have a 25GB Windows system partition (C drive) in my SSD, 2
Linux partitions (around 10GB each) and the rest is free space. However when
I run Windows I don't load the Linux partitions into the MBR (they are not
selected in Boot Edit for the Windows boot item). So when running Windows
the OS thinks the LInux partitions are part of free space outside the C
According to this article SSD performance depends on the amount of free
Unfortunately I can't find anywhere where he defines free space - is it free
space within a partition or unused space on the drive?
The question is can the SSD store data in areas which are designated as
outside any MBR defined partition thus overwriting hidden partitions?