Tried that, it crashes the machine copying it. Tried multiple machines too.[/QUOTE]
from what I read, you’re copying on the SLES9 machine. When your machine is “crashing”, what copy mechanism were you trying?
Might it be that your impression “crashes the machine” is caused by massive “i/o waits” in conjunction with FS buffer starvation? 150GB is not that much data, but when pushing that onto a slow disk (and I feel safe to assume that it’s no USB3-attached SSD you’re trying to copy to) all that data goes into the file system cache, which is far less in size. Depending on the I/O scheduler and its settings, this usually has a severe impact on the responsiveness of the whole system, as other applications that are trying to write to their files go through the same mechanisms and are effectively throttled because of your copy job.
OTOH, maybe your transfer mechanism (especially when going over the network via scp, which usually doesn’t involve file system write caching on the sending side) is too quick, compared to the read speed of the source media? Then the reads of other applications might be impacted, again giving the impression of a hanging system.
I recommend to accompany any such copy job with a run of “vmstat 1” in a separate shell on the SLES9 server - that way you can better see and judge the impact (and determine if it’s really a “hang” or just high i/o wait).