On Sat, Jul 6, 2013 at 12:34 PM, Rajko
Of course if you use hibernation that will tax swap space, but when one is worn out, after say 2000 writes, you can use different part of the disk that wasn't used that much and repeat that as long as remain disk capacity is sufficient for your needs.
That is handled transparently by the wear-leveling algorithm. ie. every time you write data to a SSD data block it picks from the available EB (erase blocks) the one with the least number of writes. I don't the process is perfect due to various design tradeoffs, but that is the goal at least. The other part of the story is the garbage collector which has the job of going through the partially used EBs and consolidating them to free EBs. When it does this the formally used EBs are erased and added to the stack of available for writing EBs. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org