<html><head>
<meta name="viewport" content="width=device-width" /><meta http-equiv="Content-Type" content="text/html;charset=utf-8" /></head><body><div class="mail_android_message" style="line-height: 1; padding: 0.5em">is it still reproducible after a fresh boot? no stale nfs or fuse mounts or similar?<br>
-- <br>
Diese Nachricht wurde von meinem Android Mobiltelefon mit <a href="http://WEB.DE">WEB.DE</a> Mail gesendet.</div><div class="mail_android_quote" style="line-height: 1; padding: 0.3em">Am 06.08.2016, 00:52, Tom Horsley <horsley1953@gmail.com> schrieb:<blockquote class="gmail_quote" style="margin: 0.8ex 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I was working on a backup script today and doing lots<br />
of runs with the --dry-run option to make sure I<br />
had things the way I wanted them.<br />
<br />
One particular filesystem I was backing up always<br />
hung right as it should have been finished. (This<br />
happened every time I did a dry run, it was 100%<br />
reproducible). Several other filesystems I was<br />
backing up had no problems of any kind with the<br />
dry run using the same command with different<br />
source and dest directories (and exclude lists).<br />
<br />
Checking all the rsync processes (this was a local<br />
file to local file rsync, so everything was on the<br />
same system), I found all 3 rsync processes sitting<br />
in a select() call, and none of them had any files<br />
open, just a couple of sockets and stdout showed up in<br />
the /proc/pid/fd directories.<br />
<br />
I added a --timeout=300 option, and that at least<br />
made it exit after 5 minutes.<br />
<br />
Later, when I removed the --dry-run option and<br />
did the real backup, the same filesystem caused<br />
no problems at all. No hang, all the backups<br />
copied OK, no errors of any kind.<br />
<br />
I just thought it was weird enough to report,<br />
but I'm unlikely to have any time to do any debugging.<br />
Just wanted to get it on record in case someone else<br />
sees it.<br />
<br />
This was on a centos 7.0 system, and I updated<br />
rsync on it just in case that fixed it, but the<br />
problem continued even after the yum update.<br />
<br />
--<br />
Please use reply-all for most replies to avoid omitting the mailing list.<br />
To unsubscribe or change options:<a href="https://lists.samba.org/mailman/listinfo/rsync" target="_blank"> https://lists.samba.org/mailman/listinfo/rsync</a><br />
Before posting, read:<a href="http://www.catb.org/~esr/faqs/smart-questions.html" target="_blank"> http://www.catb.org/~esr/faqs/smart-questions.html</a><br />
</blockquote></div></body></html>