As above really - if I put files onto the cache drive (assuming they're integrated with user shares) but, at time of the move script running, they're open or in use - how is it handled?

 

I guess the clearest example would be using the cache drive as the target for a torrent client. What happens when the client still has all the data opened?

As above really - if I put files onto the cache drive (assuming they're integrated with user shares) but, at time of the move script running, they're open or in use - how is it handled?

 

I guess the clearest example would be using the cache drive as the target for a torrent client. What happens when the client still has all the data opened?

If the file is open, it is not moved.

If the file is not open, it will be moved... so a file that is closed after each "chunk" will be moved, but the next chunk written will simply open it in its new disk location. (I don't know if your torrent client opens and closes files as it writes each piece of the file, or if it keeps the file open until it is done.  Either way, it is handled.)

 

Note: the older versions of unRAID did not check if the file was in use... That was fixed in version 4.3.2 of unRAID as seen in the release notes: http://lime-technology.com/wiki/index.php?title=Release_Notes#Changes_from_4.3.1_to_4.3.2

 

Joe L.

Thanks - that seems like the logical way for it to work!