Had a look into the parameters and changed MaxBurstLength in ietd.conf
from 262144 to 65536,
which is more decent for only 256 MB memory. Worked fine now.
Did a full copy of 2.5 GB and that went fine. After that I did a small
copy of around 200 MB, but I
got again the allocation errors on the target. While I had top running
on the target there was no swapping
and the CPU load was less than 5 (with the bigger copy it went to 7.5,
poor P-II).
So limiting the parameter MaxBurstLength doesn't fix it completely.
Albert
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
|
