NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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_oldreturned 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.
1 Reply
...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.
root is just a name, e.g. in /etc/passwd or some other authentication store. You could just as well call the account admin, and the OS itself won't care, ...
Key is the UID/GID:0 - this is what -all- U**x'es Kernel and the code care about.
There seems to be a long way ahead on your Linux learning curve. Not sure abandoning SMB in favour of NFS is a good idea therefore.
Well possible, there is -much-more around of these files and folders than U**x file and folder permissions:
Files can be secured through U**x file permissions - based on UID and GID - and through ACLs. Files with sticky bits, and files that are executable, require special security measures. What ever of these (visible and harder visible) does deny you desired action or actions.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
