Just a short question because I manually (from the Shares page) started mover: If the mover in the night kicks in, will there be two mover running in parallel or will the mover check it's own existance and exit?

 

Many thanks in advance.

Harald

 

 

Just a short question because I manually (from the Shares page) started mover: If the mover in the night kicks in, will there be two mover running in parallel or will the mover check it's own existance and exit?

 

Many thanks in advance.

Harald

 

 

The way the "mover" script is written, a file that is currently "busy" will not be moved.  "Busy" = currently being written, or read.

 

To move a given file, it must be read from the cache drive and written to its new disk.  Therefore, it will be "busy" during that process and ignored by any subsequent invocation of the "mover" script.

 

With that in mind, you can probably schedule the mover as often as you might like.  It is not necessary to do it once nightly.  You could probably do it once hourly, or every few hours.

The only issue I can thing of is a program that opens a file to write, writes a few bytes, closes the file, opens it a subsequent time, seeks to the end, appends a few bytes, closes it again, then repeats the open, seek to the end, write, close process again and again.  In between "writes" the mover script could move the partially complete file sine it had no process writing or reading it.  Somehow, I doubt of your DVD ISO writing process would do that (repeatedly open and close) as it would be grossly inefficient.

 

Joe L.

Thanks again Joe.

 

Hmm, there may two mover run in parallel? Even if there is some sort of protection for an individual file - wouldn't this stress the drives to much if there are two movers writing to the same disk for example.

 

Regards

Harald

 

 

Thanks again Joe.

 

Hmm, there may two mover run in parallel? Even if there is some sort of protection for an individual file - wouldn't this stress the drives to much if there are two movers writing to the same disk for example.

 

Regards

Harald

 

 

The "mover" script as delivered does check to see if another instance is running and will not start a second instance.

However, disks can handle more than one process writing/reading from them... the disks in your server are not too much different than the ones in corporate data centers, and they frequently handle hundreds of concurrent database queries at a time.

Maybe it should be possible if the mover in the night kicks in, will there be two mover running in parallel or will the mover check it's own existance and exit.

 

 

 

 

 

________________

Indianapolis movers

As I already said, the "mover" check to see if another instance of itself is already running.. If so, the second version just exits without doing anything as the first is already in progress.

That was another one post spammer, Joe, with a fake sig and an entire time in forum of 2 minutes.  That line was plagiarized from an earlier post.