SSD optimizer plugin, risk of data loss/corruption?

[klepp0906]

Im inching ever closer to the final product and the GO button.  SSD optimizer however... few questions.  I currently have primocache but dont use the write cache feature as its my understanding that for any benefit you'd need to enable defer writes which is the same as flushing the cache later.   If there was a crash or power loss you could end up with corrupt or missing data that wasnt written.  (or does this only apply when using ram as a cache for writes and is defer write safe with SSDs as L2?)

Either way, what im trying to ask is does the write caching used by the SSD optimizer plugin function the same way?  and as such have the same potential caveats? 

[Christopher (Drashna)]

The SSD Optimizer balancer plugin causes new files to be written to the "SSD" drives (which you can pick), and then later balanced off of those drives. 

So sudden power loss or reboots should not impact the data, at all. 

[klepp0906]

and with any type of power loss before it got shipped off or completely shipped off,  drivepool would still see it there and resume/re-send if need be?

sounds like primocache is my solution if i want a read cache, and drivepool is the solution if i want a write cache.   

[Christopher (Drashna)]

For balancing and duplication operations, the files are copied to a temp folder, and then renamed when the operation completes.  this ensures that even if an interruption occurs, that the files are intact, whole and not corrupted.   

And yeah, that's probably a good way to set things up.