When an OS (operating system) is NOT using TRIM, here is my question:
Given the fact an SSD recognizes:
a.) Free Space
b.) Valid data
c.) Stale data
1.) Does Garbage Collection actually delete Stale data on its own accord?
2.) What exactly TRIGGERS Garbage Collection to delete the aforementioned Stale data?
Rephrasing (and some background) for clarity, I know that Garbage Collection is always moving Valid data and corralling (like a cowboy) Stale data into "blocks" so that the blocks of Stale data can be deleted when the time comes (obviously, "delete" actually means "clear the block" so data may be written to it)......... So, what exactly triggers (or will trigger) the Garbage Collection function to clear those blocks?
(There are several "detailed information replete with pretty illustrations explaining Garbage Collection" that have proliferated all over the net.... however, none of them actually explain what triggers Garbage Collection on a non-trim-enabled OS.)
Thank you!
Given the fact an SSD recognizes:
a.) Free Space
b.) Valid data
c.) Stale data
1.) Does Garbage Collection actually delete Stale data on its own accord?
2.) What exactly TRIGGERS Garbage Collection to delete the aforementioned Stale data?
Rephrasing (and some background) for clarity, I know that Garbage Collection is always moving Valid data and corralling (like a cowboy) Stale data into "blocks" so that the blocks of Stale data can be deleted when the time comes (obviously, "delete" actually means "clear the block" so data may be written to it)......... So, what exactly triggers (or will trigger) the Garbage Collection function to clear those blocks?
(There are several "detailed information replete with pretty illustrations explaining Garbage Collection" that have proliferated all over the net.... however, none of them actually explain what triggers Garbage Collection on a non-trim-enabled OS.)
Thank you!