Promin, ale to stale IMHO nemuze dobre fungovat. Proved si pomyslne par ruznych zapisu do vice bunek a zjistis, kde je problem (ale take je mozne ze to reseni proste stale nevidim). Bez TRIMu to proste dost dobre nejde (leda by nahradni kapacita byla 100% kapacity disku), ostatne neco podobneho se pise v jednom z tech odkazu, ktere jsem postnul.
http://www.t10.org/ftp/t10/document.08/08-347r1.pdf TRIM jako security problem (mimo jine)
http://lwn.net/Articles/293658/ zde je vysvetlen problem WL pri zaplnenem disku, citace:
If the device fills up with data, that list of free blocks can get quite short, making it difficult to deal with writes and compromising the wear leveling algorithm. This problem is compounded by the fact that the low-level device does not really know which blocks contain useful data. You may have deleted the several hundred pieces of spam backscatter from your mailbox this morning, but the flash mapping layer has no way of knowing that, so it carefully preserves that data while scrambling for free blocks to accommodate today's backscatter. It would be nice if the filesystem layer, which knows when the contents of files are no longer wanted, could communicate this information to the storage layer.
Ano, problem se mirne oddali pouzitim dodatecne kapacity, ale neni to ani zdaleka totez, jako kdyby WL mohl vyuzivat celou kapacitu disku.