--timeout not honoured
Hi I already wrote about this problem half a year ago but didn't get an answer: http://lists.samba.org/archive/rsync/2009-June/023412.html I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800. But still I often have rsync stall much longer than that. Some examples: 2009/12/14 23:14:35 [8707] io timeout after 11670 seconds -- exiting 2009/12/14 23:14:35 [8707] rsync error: timeout in data send/receive (code 30) at io.c(239) [sender=3.0.3pre1] 2009/12/14 00:20:04 [19046] io timeout after 15485 seconds -- exiting 2009/12/14 00:20:04 [19046] rsync error: timeout in data send/receive (code 30) at io.c(239) [sender=3.0.3pre1] 2009/12/12 22:15:21 [29732] io timeout after 8082 seconds -- exiting 2009/12/12 22:15:21 [29732] rsync error: timeout in data send/receive (code 30) at io.c(239) [sender=3.0.3pre1] 2009/12/11 23:14:23 [30216] io timeout after 11613 seconds -- exiting 2009/12/11 23:14:23 [30216] rsync error: timeout in data send/receive (code 30) at io.c(239) [sender=3.0.3pre1] I know that 3.0.3pre1 is not the newest version, but as this is running on a NAS it's not that easy to update or compile a newer version. However, why is it that rsync waits much longer than given in --timeout? Shouldn't timeout work that way? Thanks bye Fabi -- 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
DO NOT REPLY [Bug 4621] Option to create ancestors of destination, like "mkdir -p"
https://bugzilla.samba.org/show_bug.cgi?id=4621 li...@elasticmind.net changed: What|Removed |Added CC||li...@elasticmind.net --- Comment #4 from li...@elasticmind.net 2009-12-15 06:12 CST --- Greetings, I just noticed my rsync backup scripts failing and discovered it was due to a missing ancestor of the remote target directory. I immediately searched for a tunable that would signal rsync to use 'mkdir -p' instead of just 'mkdir' when initially creating the target directory, but didn't seem to find one. I agree with everyone else that it would be incredibly useful for rsync to either adopt such behaviour by default (assuming always doing 'mkdir -p' isn't harmful in any way), or have a tunable to enable it. Kind regards, moggie -- 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
Uninstalling rsync 3.0.6
Hello, I have installed rsync from source but when i want to remove it im not able to do it can anyone help me that would be great. Kind regards, Andy -- 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
Re: retransfer fail of large files with inplace and broken pipe
OK, have tried now --inplace with --backup option but syncing the files does consume much more time than a normal rsync process, so this is not a reliable solution. Thx Tom "Tom" schrieb im Newsbeitrag news:hg7dg6$em...@ger.gmane.org... > Hi, > > retransfer of large fail with inplace after a broken pipe is working now. > (thx again to wayne) > > but it is much more slow as if a "normal" rsync job. > > I have read that setting the --backup option could help. (have not tried > it > yet) > > But --backup option would halve the space, which is not desirable. > > Is there a way to tell rsync to delete the --backup file after an > successful > sync. > > thx > Tom > > > "tom raschel" schrieb im Newsbeitrag > news:loom.20091213t075221-...@post.gmane.org... >> Hi, >> >> i have to tranfer large files each 5-100 GB (mo-fri) over dsl line. >> unfortunately dsl lines are often not very stable and i got a broken pipe >> error. >> (dsl lines are getting a new ip if they are broken or at least after a >> reconnect every 24 hours) >> >> i had a script which detect the rsync error and restart the transmission. >> this means that if a file has transfered e.g. 80 % i start again from >> beginning. >> >> using partial and partial-dir was no solution to resync because rsync cut >> the >> original file (e.g. from 20 GB to 15 GB) which means that i have to >> transfer >> the whole rest of 5 GB. >> >> so i had a look at --inplace which I thougt could do the trick, but >> inplace is >> updating the timestamp and if the script start a retransfer after a >> broken pipe >> it fails because the --inplace file is newer than the original file of >> the >> sender. >> >> using ignore-times could be a solution but slow down the whole process to >> much. >> >> is there a option to tell rsync not to change the time of a --inplace >> transfered file, or maybe preserve the mtime and do a comparison of mtime >> instead of ctime. >> >> Thx >> Tom >> >> >> >> -- >> 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 >> > > > > -- > 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 > -- 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
Re: Option to create ancestors of destination, like "mkdir -p
> I agree with everyone else that it would be incredibly useful for rsync to > either adopt such behaviour by default (assuming always doing 'mkdir -p' isn't > harmful in any way), or have a tunable to enable it. I also agree the suggested behavior makes a lot of sense and I think it is a good idea. However, some deployments may rely upon the current behavior. As an example, a setup may rely on rsync failing if a file system is not mounted. In such a situation, it is worth contemplating whether you would you want rsync to generate the mount point and any subdirectories, specified for this rsync. I personally think that such checks should be external from rsync. However, changing the current default behavior has the potential to create problems on setups which may rely on the current default behavior. I recommend the consideration of potential problems which could occur if the deployed setups are dependent on the current rsync behavior and that default behavior changes. Then based upon the severity of these potential problems move ahead or delay the change to a major revision change? My 2ç -- 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
Re: --timeout not honoured
At 10:27 15.12.2009 +0100, Fabian Cenedese wrote: >Hi > >I already wrote about this problem half a year ago but didn't get >an answer: http://lists.samba.org/archive/rsync/2009-June/023412.html > >I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800. >But still I often have rsync stall much longer than that. > >2009/12/14 23:14:35 [8707] io timeout after 11670 seconds -- exiting >2009/12/14 23:14:35 [8707] rsync error: timeout in data send/receive (code 30) >at io.c(239) [sender=3.0.3pre1] > >2009/12/14 00:20:04 [19046] io timeout after 15485 seconds -- exiting >2009/12/14 00:20:04 [19046] rsync error: timeout in data send/receive (code >30) at io.c(239) [sender=3.0.3pre1] > >However, why is it that rsync waits much longer than given in --timeout? >Shouldn't timeout work that way? I think I know now where my confusion comes from. The reported time is not the actual time without action but the time since the start of the rsync command. 2009/12/15 20:00:02 [4260] building file list 2009/12/15 20:00:03 [4260] .d..t.. vmware/FTPServer2/ 2009/12/15 20:23:45 [4260] https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
