On Mon 25 Apr 2005, Jeroen van Wolffelaar wrote: > > > > That's pretty strange, I've never heard of the sending rsync eating > > memory if the receiving end can't write its output. It would be helpful > > if you could check to see what exactly is eating the memory; I rather > > doubt that it was rsync.
> It is the rsync --server --sender <bla bla> process for sure. (The sender...) > What exactly do you mean? Cut&pasted from 'top' on merkel from this > morning: > > 13947 jeroen 20 0 13.2G 12G 1200 R 4.0 26.2 2:02 rsync > > (sorry but due to the hurry involved getting merkel responsive again I > killed before copy&pasting the full command line, I did check it though, > and it *was* the recieving part of the above-mentioned sync. receiving or sending?! > Ok, retried: > > [EMAIL PROTECTED] df -h /org/qa.debian.org/data/bts2ldap > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/vg0-backup > 31G 29G 4,0K 100% /org/backup > [EMAIL PROTECTED] rsync -a --delete merkel:/org/qa.debian.org/data/bts2ldap/ > /org/qa.debian.org/data/bts2ldap Tip: -H might also be useful if there are hard links. > rsync: write failed on "/org/qa.debian.org/data/bts2ldap/fullindex": No space > left on device (28) > rsync error: error in file IO (code 11) at receiver.c(290) > rsync: connection unexpectedly closed (137 bytes received so far) [generator] > rsync error: error in rsync protocol data stream (code 12) at io.c(420) > [EMAIL PROTECTED] > > And while this error was already there, and exited, on merkel the rsync > process was still growing and eating space: > > merkel$ ps aux : > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > jeroen 18862 0.0 8.4 4215424 4211296 ? R 16:12 0:23 rsync --server > --sender -logDtpr . /org/qa.debian.org/data/bts2ldap/ > > That's 4GB in a dozen of seconds. > > And I needed to kill -9 it (maybe normal kill would have worked with more > patience though) Would it be possible to do a strace on it? Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
