(SOLVED)Random .tmp files being created and then deleted

[omfgunraid]

Hello everyone,

 

So I have added an extra HDD in my array and it's too early for it to be there. I have to fill up my existing drive. Now, I've set it up so that this "empty" drive spins down, however it does not remain so. Sometimes it gets some "action" in the form of random .tmp files being created and then rapidly deleted, as seen below:

 

** Disk 2
Jan 13 18:55:08 CREATE => /mnt/disk2/230875907.tmp
Jan 13 18:55:08 OPEN => /mnt/disk2/230875907.tmp
Jan 13 18:55:08 DELETE => /mnt/disk2/230875907.tmp
Jan 13 20:01:03 CREATE => /mnt/disk2/660760271.tmp
Jan 13 20:01:03 OPEN => /mnt/disk2/660760271.tmp
Jan 13 20:01:03 DELETE => /mnt/disk2/660760271.tmp

Any idea how to find out what docker container is creating them?

I would do it the old fashioned way: close all and open them one by one.. but maybe someone knows a simpler way?

 

Cheers!

[Squid]

If those times are corresponding with you running the tests in Fix Common Problems, then what you're seeing is normal.

[omfgunraid]

Thanks Squid, that was it!

 

Weirdly, after I went to bed I found another set of .tmp files being created at 4:00 this night. It might have been that the plugin also triggered then as well.

 

Anyway, the mistery is solved and visible for posterity!

[Squid]

Thanks Squid, that was it!
 
Weirdly, after I went to bed I found another set of .tmp files being created at 4:00 this night. It might have been that the plugin also triggered then as well.
 
Anyway, the mistery is solved and visible for posterity!

You can also enable avoid disk spinups in FCP where it will skip filesystem tests (reading and writing a file) in sounds down disks

Sent from my SM-T560NU using Tapatalk