NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
nfs
6 Topics
Issue with old user permissions and NFS
I recently migrated my RN214 to expose NFS shares instead of SMB (no Windows PCs anymore). Turned out that there was a UID collision, user "volker" was auto-assigned UID 100 which I didn't care too much back then. Now, with NFS, UID 100 reflects to systemd-network on my local PC and the system would not let me change attributes, rsync was throwing erros similar to sync: [generator] failed to set permissions on "/media/rn214-Media/somefile": Operation not permitted (1) . So I created a new user "volker" on the RN214 (changing the existing UID was not possible) with UID 1000 which is the same on the local PC after first renaming the existing user volker to "volker_old". This new "volker" can read and write to files owned by "volker_old", copy them around and even delete them, but he can't get ownership of the existing file nor change permissions. Now I have numerous files owned by "volker_old" that I want to transfer to "volker". So I figured running find /data/Media -user volker_old -exec chown volker:users {} \; in a shell on the RN214 would be an elegant solution to this, since find /data/Media -user volker_old returned plenty of hits. However, I get chown: changing ownership of '/data/Media/somefile': Operation not permitted errors, even as admin user belonging to the admin group. sudo does not exist and for su - I don't know the root password - if there is any. Sure, I could just delete all the offending files and copy them over from a backup again, but this is about 5TB of data and will take an eternity. Is there any way to resolve this ownership issue efficiently? Any help highly appreciated.Solved186Views0likes7Comments
Character encoding, Codepages, SMB/CIFS and NFS
We've got 4 ReadyNAS in operation. The 2 oldest units run RAIDiator: v4.1.16 with Samba v.3.6.25 and cannot be upgraded anymore. Microsoft finally decided to dump SMBv1 and all machines on our network got upgraded to a life without SMBv1 hence the 2 old NAS were no longer available to the network. To resolve this issue we decided to enable NSF and disable SMB/CIFS. Microsoft was nice enough to include the NSF-Client and server in their updates. This way we can keep them units on the Network and in production as redundant backups of backups - we first thought. We we're able to map the shares to Windows 10, read and write data for testing, etc. all is operational. So far so good and almost too nice to be true. But there is a problem! Folder- & file-names that use special characters changed their appearance. For instance all Umlaut like äöü became double characters. eg. the letter "ü" displays as double character "ü" in NSF-client. Yep it's an issue directly related to varying codepages. Apparently the NAS OS (RAIDiator) uses varying codepages for SMB/CIFS and NSF. The option for language selection in Frontview is missleading. To be on the safe side one would have to select english ASCII. By selecting any Unicode option incompatibility between SMB/CIFS and NFS filesystems/protocols gets in effect without any mention. This is not documented by Neatgear (at least we could not find anyting). We assume we're not the first and only customers experiencing this senselessness and would like to learn wether there is a solution that we might have missed. Looking forward to receiving responses.4.7KViews0likes7CommentsHow long to reinstall OS on RN102
I have an RN102 that has been giving me headaches as of late under heavy NFS load. It's providing NFS shares for a ProxMox Virtualization (Hypervisor) system. Lately, when under heavy load, particularly when migrating qcow2 disk files from one NFS Share on one disk in the NAS to another NFS share on another disk in the NAS, the system locks up and becomes unresponsive to anything but pings. Web UI is non-responsive and the NFS shares drop off the network (Proxmox no longer sees them). To try and solve this, I did an OS Reinstall per the documentation. Started the reinstall around 8pm one evening and at 7:30am the following morning, the power LED on the NAS was still flashing as if the OS reinstall was still in progress. Not sure what to do next with this. Do I leave it and hope it finally completes? I'm not in front of the NAS now, so I don't recall the specific model, just that it's a 100 series RN102. It is on the latest production firmware available from Netgear. Thanks in advance for any info or suggestions.1.9KViews0likes2CommentsShare NFS User ID Mapping Configuration: where?
6.8.0 release notes says that with this release "Share NFS User ID Mapping Configuration" has been added, however I cannot find where this can be configured... I searched in all my readynas admin configuration withoung finding itSolved2KViews0likes2Commentsnfs: access control according to linux user
ReadyNas 21200 I'm accessing the nas shares by nfs from a linux box I have an user giuseppe on the nas I have an user giuseppe and an user maria on the linux box When I access the nas from my linux box I want to give: - full rw access to the files on a given share to linux user giuseppe - no access to the same files to linux user maria How do I get it?3.2KViews0likes3CommentsNFS Performance issues
I work for Netapp in the NFS support area. I puchased this device almost a year ago and for the most part have been happy to have it just as a storage device. Recently I tried to put a VM on the device. Mounted nfsv3, and default mount parameters. The mount is fine, however performance is absolutely terrible. I took a packet trace to see if it potentially could be network loss. There were a few packets that appear to be loss, but VERY little and they do not correspond with the latency that i'm seeing. I am seeing upwards of 20 seconds for a single write call. I can send the trace out to you, but I dont see a way to attach it to this post. I downloaded gcc5.4 and attempted to untar. The untar process took 3min 54s to complete. The file was stored on the filer, so this would be a read and write. This was intentional to gauge performance. I need assistance to see what I can do to get better performance out of this. I dont expect the world, but I do expect to be able to install updates on a windows vm in under 10 hours. (Local disk it is ~15 minutes). If there is anything / logs / traces / additional tools to run, please let me know.4.3KViews0likes8Comments