This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Just updated to 6.5.1 this morning and suddenly, all files in all directories have been updated with incorrect/bogus creation and modification dates. Using this in a shared/mult-user setting where we rsync files between local system and the ReadyNAS, we're having huge issues as all files are in conflict. It also seems files are being updated with user/group of root/root when each file should be owned by our own users.
Re: OS 6.5.1 set bogus creation/modification dates
It looks like the culprit was Amazon Cloud Drive sync. I think the reason 6.5.1 exposed the issue was it introduced "support for bi-directional sync with Amazon Cloud Drive accounts" per the release notes email I received from Netgear.
So, if you use Amazon Cloud Drive sync, I suggest not upgrading to 6.5.1 until you have it turned off. Any then maybe after you upgrade, don't turn it back on? I'm not sure. I don't need to use it, so I'm going to leave it off.
Re: OS 6.5.1 set bogus creation/modification dates
I just downgraded to 6.5.0 and the setting of incorrect creation/modification dates seems to have stopped, but everything it touched is still wrong. Spot checking directories it looks like almost all files were touched, so this remains a big issue.
Re: OS 6.5.1 set bogus creation/modification dates
It looks like the culprit was Amazon Cloud Drive sync. I think the reason 6.5.1 exposed the issue was it introduced "support for bi-directional sync with Amazon Cloud Drive accounts" per the release notes email I received from Netgear.
So, if you use Amazon Cloud Drive sync, I suggest not upgrading to 6.5.1 until you have it turned off. Any then maybe after you upgrade, don't turn it back on? I'm not sure. I don't need to use it, so I'm going to leave it off.
