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!
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.
I have installed the 6.4 T29-version. Backup still fails. The problem becomes really urgent, because the NAS gets dramatically slower (as I mentioned before). It's no longer possible to work in a normal way. Sometimes I have to wait 20s or more to get the content of a network folder. Please help!
As suggested I switched off/on the RSYNC protocoll. Here the result from my linux system log. Timeouts as before. And the NAS becomes slower and slower. Would it be a solution to reinitialize the system, upgrade to 6.2.5 and reload all files? (I would loose all my snapshots wouldn't I. Not a nice perspective.) But in the state as the NAS runs now it's practically of no use.
2015/11/09 23:11:06 [2125] connect from UNDETERMINED (192.168.10.3) 2015/11/09 22:11:06 [2125] rsync on BackupVbox/ from vboxer@UNDETERMINED (192.168.10.3) 2015/11/09 22:11:06 [2125] building file list 2015/11/09 22:17:32 [2125] UNDETERMINED send Machines/Joomla/Snapshots/{7bf224d4-46a8-4931-839a-52c828317899}.vdi 10830741504 416351 2015/11/09 22:18:15 [2125] [sender] io timeout after 32 seconds -- exiting 2015/11/09 22:18:15 [2125] rsync error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.1] 2015/11/09 23:18:38 [2233] connect from UNDETERMINED (192.168.10.3) 2015/11/09 22:18:38 [2233] rsync on BackupVbox/ from vboxer@UNDETERMINED (192.168.10.3) 2015/11/09 22:18:38 [2233] building file list 2015/11/09 22:24:15 [2233] UNDETERMINED send Machines/Joomla/Snapshots/{7bf224d4-46a8-4931-839a-52c828317899}.vdi 10830741504 416351 2015/11/09 22:25:12 [2233] [sender] io timeout after 30 seconds -- exiting 2015/11/09 22:25:12 [2233] rsync error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.1]
As my NAS after update to 6.4 it's hardly possible to work normaly I did a search and found, that many people have the same problem with the slowness of the system, even worse than I have. From what I read I suppose that the tomeouts with rsync are just a consequence of the slow access time with 6.4 maybe becose of the new quota system. I have to make no a decision soon, wether to initialize the system and upgrade to 6.2.5 and load my data to get a normally running NAS (but therefore loose all snapshots). For to make that cecision it would be very helpful to know, wether a new release of ReadyNas can be expected in the next days.
I tried that also - no difference for me. (I didn't really expect a difference as the rsync service is not used when doing a local backup, so its all in that --timeout- option being passed on the command line).
This is a major concern as I have NO RELIABLE BACKUPS of my ReadyNAS unless I log in on the command line and run it manually!
the main problem for me is not the backup with rsync but the incredibly slow response time with cifs access. I noticed that this responsetime depends on the directories. There are some directories without problems but on some others, allways the same ones, the problem is permanent. Should I state my problem in an other forum?
as you sugested I tried to reset the permissions (in file access of a share). That produced an error:
"Cannot set file access. Check if specified user or group exists. facl_change fail uid=99 gid=99 Code 1007130001 I checked the specified group = share = 101
and the user = admin = 98"
Continuing with ignore doesn't help. The reset is logged as finished but the very slow access continues.
I have been troubleshooting my NAS and have found the exact same problem. I can't reset permissions anymoew for my shares due to that same error. I have just updated the NAS to that latest version. I have the 316 model NAS.
error txt
facl_change fail uid=99 gid=99
Code: 1007130001
Need this fixed ASAP! Is there any other way to change the permissions for access?
The issue I run into quite regularly is I have access to Share 2 but not share 1. They seem to have identical permissions setup the only difference I can see is that number after guest... 1018 compared to 154.... does that mean anything to anyone?
