Jason Cox
2004-Oct-05 07:38 UTC
Rsync 2.6.3 not releasing memory under Mandrake 10 Official
Hello, I have been having trouble with a Mandrake 10 Server. When I copy from one server to another I find that on completion of the Rsync command that the system still reports back that the memory is in use ( aprox 1 gig ). I have installed 1.5 gig of ram into the server and it made no difference. On the latest occasion I dropped back to single user and It didn't release the memory. There doesn't appear to be any entry's under /proc for Rsync or the high memory use. The only solution I have is to reboot the server each time a Rsync task is run. This problem also existed with the version of Rsync that shipped with Mandrake 10. Server specs Athlon XP 2400+ 1.5 Gig ram 340 gig HD 100Mbit Ethernet 2.6.3-7 Mandrake kernel ( UP-enterprise) I can supply further information if required Regards Jason Cox System Administrator Multiskilled Resources Australia Pty Ltd ph 02 4908 0000 (office) ph 02 4908 0015 (direct) mob 0423 600 156 fx 02 4942 4125 email jason.cox@multiskilled.com.au
Paul Slootman
2004-Oct-05 08:07 UTC
Rsync 2.6.3 not releasing memory under Mandrake 10 Official
On Tue 05 Oct 2004, Jason Cox wrote:> I have been having trouble with a Mandrake 10 Server. > When I copy from one server to another I find that on completion of the > Rsync command that the system still reports back that the memory is in useWhen a process goes away, any memory that process may have used is released.> ( aprox 1 gig ). I have installed 1.5 gig of ram into the server and it made > no difference. On the latest occasion I dropped back to single user and It > didn't release the memory. There doesn't appear to be any entry's under > /proc for Rsync or the high memory use. The only solution I have is to > reboot the server each time a Rsync task is run.You don't show any concrete examples of how you determined this memory usage. I get the feeling you may be fooled by the way linux uses available memory for the buffer cache etc.. So, please show the commands you're using to determine that the memory is not being freed, together with the output of those commands. Paul Slootman