NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Modification time preservation issue using SMB in certain configurations with ReadyNASOS 6
Hi! I ran across a quite weird behaviour where modification time stamps of the local file system were not preserved after copying the file to a SMB share on my Netgear ReadyNAS 214 from a Linux c...
VolkerB wrote:
I ran across a quite weird behaviour where modification time stamps of the local file system were not preserved after copying the file to a SMB share on my Netgear ReadyNAS 214 from a Linux client. After copying, the file received the current time as modification time instead. That behaviour seems to depend on certain versions of the client SMB version, the server SMB version and the negotiated SMB protocol version.
Why is that an issue? Because mirroring directories with rsync with the strategy to overwrite older files does not work properly anymore.
Have you tried enabling rsync on the share, and making the share the rsync target (instead of mounting it with SMB)? That works with my own NAS->NAS backups with no issues.
FWIW, I don't think Netgear will update SAMBA on the NAS, unless a security update requires them to do so. Even then, they might just back-port the security fix. They've clearly exited their NAS business.
Please excuse the brevity, wresting the forum frontend is not exactly my forte.
StephenB wrote:
VolkerB wrote:I ran across a quite weird behaviour where modification time stamps of the local file system were not preserved after copying the file to a SMB share on my Netgear ReadyNAS 214 from a Linux client. [...]
Why is that an issue? Because mirroring directories with rsync with the strategy to overwrite older files does not work properly anymore.
Have you tried enabling rsync on the share, and making the share the rsync target (instead of mounting it with SMB)? That works with my own NAS->NAS backups with no issues.
FWIW, I don't think Netgear will update SAMBA on the NAS, unless a security update requires them to do so. Even then, they might just back-port the security fix. They've clearly exited their NAS business.
No, I didn't try rsync directly but I'm quite sure it would work. However in my case I need mounts to be accessible on demand, hence I have something like
//rn214 /media/rn214/media cifs noauto,users,credentials=/home/user/.smbcredentials,iocharset=utf8,uid=1000,gid=1000,file_mode=0770,dir_mode=0770 0 0
in fstab and added
[public]
# This share allows anonymous (guest) access to /home/public without authentication
# Created with bindfs in /etc/fstab with
# /home/public /media/public fuse.bindfs perms=0777,create-with-perms=0777 0 0
comment = Public share. Everyone can read and write.
path = /media/public
read only = no
guest ok = yes
guest only = yesto smb.conf.
Pity to hear that Netgear will discontinue it's NAS boxes, I found the RN214 to be among the better ones on the market. I'll continue to use it "as is" (it's behind a firewall anyway and not allowed to talk to "the internet") and hope that future client updates won't break anything. My post was just meant to sensitize people to look for weird things with timestamps when they copy files to a SMB share on a ReadyNAS.
VolkerB wrote:
Pity to hear that Netgear will discontinue it's NAS boxes, I found the RN214 to be among the better ones on the market. I'll continue to use it "as is" (it's behind a firewall anyway and not allowed to talk to "the internet") and hope that future client updates won't break anything.
FWIW, I am also planning to continue to use mine "as is" as long as they work. Mine are just used for storage, so also not exposed to internet traffic.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
