Forum Discussion

Apprentice

Nov 01, 2015

Bug Report: Firmware 6.4.0 Rsync Timeout

Hello

Really one for Netgear support (posted here as I don't know how else to submit it).

I use rsync to backup my ReadyNas 314 to an external eSATA drive.

I had similar issues to others reported here when doing the upgrade (drive connection names changed), but got over all that and re-created the backup job.

Prior to the update, my rsync backups (not network, I must add, always local drive->esata, using rsync with host name = localhost) were working OK.

After the upgrade to firmware 6.4.0, the backup job fails, always on one single file, which happens to be my very large MS Outlook mailbox.

The error is also always the same (found by inspection of the backup log file). It is the dreaded rsync timeout error.

This can be traced back the how rsync is invoked (ps -eaf shows); rsync is being invoked with command line option --timeout=30.

This timeout is too short.

Unfortunately, the rsync backup is started by a binary, not a script, so its not possible to just do a quick manual patch work around.

REQUEST FOR NETGEAR: Please change the timeout applied on the command line to a higher number (60 - 600 seconds).

Even better: please provide an option through the web interface dialogs where we can specify whatever timeout period we like. It can be optional / defaulted so that those not sufficiently tech savvy can ignore it.

As it stands, I can't get a reliable backup - of my email, which is kind of important!

Thank you

ReadyNAS Backup

18 Replies

Replies have been turned off for this discussion

BrianL2
NETGEAR Employee Retired
Nov 02, 2015
Hi quickly_now,

Try the latest Beta Firmware for OS6 Series NAS (found here).

Let me know if this addresses both your issues with your external USB hard drive and rsync backup.

Kind regards,

BrianL
NETGEAR Community Team
- quickly_now
  Apprentice
  Nov 05, 2015
  Thanks BrianL
  
  It took me a couple of days to be able to to do this at a non-critical time (the ReadyNAS is used all day every day in business).
  
  I have done the update to the beta firmware.
  
  No joy I'm afraid - if anything its worse, lots of io timeouts after 30 seconds. The --timeout=30 option is still being passed on the command line. No new options through the web interface to change that option or to remove it.
  
  If anything this is a step back, as I'm no getting timeouts in places I did not get before. And as the beta release notes make it clear, rolling back does not seem to be an option.
  - quickly_now
    Apprentice
    Nov 06, 2015
    More information:
    
    Using ps I was able to get the command line, and then ran rsync to do my eSata backup, omitting the --timeout=30 option.
    
    All works fine.
    
    So the command line I used was:
    
    rsync -v -8 --recursive --links --times --omit-dir-times --omit-link-times --devices --specials --modify-window=1 --delete --owner --group --acls /tmp/10219/data localhost::ESATA_HDD_4/
    
    This works fine.
    
    Suggestion: please allow us to change the timeout period. --timeout=30 is too short.