I think I've seen some mysterious issues like this on high-use network drives, and some sleep never hurt anyone. I suppose a programmatic pre-read sleep might help or a post-write sleep. What program wrote that dataset that becomes the input for the 3dcopy? You could wrap 3dcopy in a script to include a delay before and after, maybe making the amount of sleep different if the input and output is compressed. That might be a good test to see if this is actually useful. You could also try turning off compression completely when running this on a server by unsetting AFNI_COMPRESSOR and setting AFNI_AUTOGZIP to NO.
Edited 2 time(s). Last edit at 08/31/2022 05:27PM by Daniel Glen.
