Out of memory in make_file

Kelly Kane kelly at hq.newdream.net
Wed Apr 4 17:04:37 GMT 2007

Carson Gaspar wrote:
> Kelly Kane wrote:
>> bottom:~# free
>>             total       used       free     shared    buffers     cached
>> Mem:       3090232    3068536      21696          0        164    
>> 2289396
>> -/+ buffers/cache:     778976    2311256
>> Swap:            0          0          0
> Is that output while rsync is running? rsync can eat a _lot_ of RAM, 
> although newer versions use less.
> That's mostly useless. Try ulimit -a.

I have done further testing on the machine, and yes, the `free` output 
reported above is pretty consistent regardless of when rsync crashes. It 
is difficult to get an exact memory report just before it crashes, 
sometimes it takes 30+ minutes to die. Do you have any suggestions for 
snagging that debugging output?

# ssh bottom ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
max nice                        (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) unlimited
max locked memory       (kbytes, -l) unlimited
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) unlimited
max rt priority                 (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) unlimited
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited


More information about the rsync mailing list