https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #6 from roland ---
nobody has a clue?
i think proper rsync timeout handling is important.
i have had whole nightly backup procedures hung for the whole night because
rsync got stuck and didn't get timeout, i.e. machines did not get
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #5 from roland ---
apparently, this is causing the problem:
if (am_receiver) {
return;
}
if i comment out the return statement, things work again.
@wayne, what is the reason that timeout checking
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #4 from roland ---
here with debug=all
working correctly
# /root/rsync/rsync-3.2.5/rsync -avi --timeout=5 --exclude='/proc'
--exclude='/dev/' --exclude='/sys' --debug=all --msgs2stderr
root@172.20.37.189:/iscsipool
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #3 from roland ---
ah, getting a clue
in io.c
static void check_timeout(BOOL allow_keepalive, int keepalive_flags)
{
time_t t, chk;
/* On the receiving side, the generator is now the one that decides
* when
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #2 from roland ---
here is another bugreport, where timeout is not effective/working
https://bugzilla.redhat.com/show_bug.cgi?id=1944132
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #1 from roland ---
here is some strace from the backup host to show the difference
if i set timeout=60 , rsyncing "root@172.20.37.189:/" hangs forever:
08:25:30 select(4, [3], [], [3], {tv_sec=30, tv_usec=0}) = 1 (in [3], left
https://bugzilla.samba.org/show_bug.cgi?id=15163
Bug ID: 15163
Summary: rsync timeout non-effective
Product: rsync
Version: 3.2.0
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
apparently, it must be a bug
if i do
/root/rsync/rsync-3.2.5/rsync -avi --timeout=10 --exclude='/proc'
--exclude='/dev/' root@172.20.37.189:/ /zfspool/backup/172.20.37.189/
it hangs forever , as soon as rsync tries to traverse the
suspended/hanging /iscsipool on the remote machine
if i do
there is connection timeout and I/O timeout
i'm using the I/O timeout.
for "--timeout" manpage is "if no data is transferredthen rsync will
exit"
no data is being transferred for hours, but it doesn't exit.
so, what's the problem here ?
--timeout=SECONDS
This
You are using rsync over ssh. The connection timeout (and port) options
don't matter if rsync isn't doing the networking.
On 9/1/22 08:49, Roland via rsync wrote:
hello,
i do some backup via rsync/ssh and pull data from remote machine to
local machine.
whenever on remote machine there is
hello,
i do some backup via rsync/ssh and pull data from remote machine to
local machine.
whenever on remote machine there is some network attached subdir getting
"stuck" (i.e. read/write is blocking, eg. by suspended zfs pool because
of error), rsync backup also hangs forever.
i wonder what's
11 matches
Mail list logo
