https://bugzilla.samba.org/show_bug.cgi?id=5567

           Summary: REGRESSION: 3.0.3pre3 dies with "failed to open XXX,
                    continuing: Too many open files"
           Product: rsync
           Version: 3.0.3
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
         QAContact: [EMAIL PROTECTED]


I started getting a lot of errors like

rsync: failed to open
"/tftpboot/moniscreen/usr/src/linux-headers-2.6.24-19-generic/include/config/fs/posix/acl.h",
continuing: Too many open files (24)
rsync: failed to open
"/tftpboot/moniscreen/usr/src/linux-headers-2.6.24-19-generic/include/config/fujitsu/laptop.h",
continuing: Too many open files (24)
rsync: failed to open
"/tftpboot/moniscreen/usr/src/linux-headers-2.6.24-19-generic/include/config/fuse/fs.h",
continuing: Too many open files (24)
rsync: failed to open
"/tftpboot/moniscreen/usr/src/linux-headers-2.6.24-19-generic/include/config/fusion/ctl.h",
continuing: Too many open files (24)
rsync: failed to open
"/tftpboot/moniscreen/usr/src/linux-headers-2.6.24-19-generic/include/config/fusion/fc.h",
continuing: Too many open files (24)
rsync: failed to open
"/tftpboot/moniscreen/usr/src/linux-headers-2.6.24-19-generic/include/config/fusion/lan.h",
continuing: Too many open files (24)
rsync: failed to open
"/tftpboot/moniscreen/usr/src/linux-headers-2.6.24-19-generic/include/config/fusion/logging.h",
continuing: Too many open files (24)
rsync: failed to open
"/tftpboot/moniscreen/usr/src/linux-headers-2.6.24-19-generic/include/config/fusion/sas.h",
continuing: Too many open files (24)

after I upgraded from rsync 3.0.3pre2 to 3.0.0pre3. I invoke rsync on a debian
stable system on x86 with the following arguments/environment:

execve("/usr/bin/rsync", ["rsync", "--numeric-ids", "--delete",
"--delete-after", "-ax", "[EMAIL PROTECTED]:/", "/tftpboot/moniscreen"],
["SHELL=/bin/bash", "TERM
=screen", "USER=root", "http_proxy=http://proxy.kurp.hut.fi:3128/";,
"SUDO_USER=lindi", "SUDO_UID=548", "ftp_proxy=http://proxy.kurp.hut.fi:3128/";,
"PATH=/usr/local/sb
in:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin"...,
"PWD=/root", "EDITOR=/home/lindi/bin/editor", "SHLVL=1",
"SUDO_COMMAND=/bin/bash backup2 --stdin",
 "HOME=/home/lindi", "LESSCHARSET=latin1", "LOGNAME=root", "LC_CTYPE=fi_FI",
"SUDO_GID=500", "_=/usr/bin/strace"])

and with the following ulimits:

core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) 1004140
max nice                        (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) unlimited
max locked memory       (kbytes, -l) 1004140
max memory size         (kbytes, -m) 1004140
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) 4096
cpu time               (seconds, -t) unlimited
max user processes              (-u) unlimited
virtual memory          (kbytes, -v) 1004140
file locks                      (-x) unlimited

I could raise ulimit of open files but shouldn't rsync cope just fine with the
default limit?

The diff between pre2 and pre3 is quite small but I was unable to figure out
anything obvious. What extra info should I provide? The whole strace output is
96 megabytes and contains sensitive data. I was unable to reproduce the issue
with a simple

mkdir a
for i in `seq 1 4096`; do echo > a/$i; done
rsync --numeric-ids --delete --delete-after -ax a/ b


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Reply via email to