You cannot change ownership of mounted filesystems. That must be done from the remote end. Only the contents can be modified when you have permissions. You will probably need to figure out what the expected options are on the NFS mount command. We mount our NAS at work as remote home directories. We have this long line of options. I suspect some (but not all) of these will apply.
Output of mount with no options (and only my remote home directory being shown): bilbo.arrs.arrisi.com:/vol/users/users/lbrigman/private on /users/lbrigman type nfs (rw,nosuid,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.109.0.189,mountvers=3,mountport=4046,mountproto=udp,local_lock=none,addr=10.109.0.189) showmount only shows the exported mount points not the permissions of the mount. sudo showmount -e 10.109.0.189 Export list for 10.109.0.189: /vol/departments (everyone) /vol/cifs_01 (everyone) /vol/isos (everyone) /vol/vm_align01 10.109.80.0/23,10.109.86.0/24 /vol/cvinstall (everyone) /vol/vol0/home (everyone) /vol/vol0 austria.arrisi.com,highlands.arrisi.com /vol/export2 (everyone) /vol/data_arwen (everyone) /vol/vm_isos 10.109.80.0/23,10.109.86.0/24 /vol/maupin2 (everyone) /vol/users (everyone) Notice that the actual mount point is not the exported mount point but a directory further in the tree. Here is my actual mount command: mount -t nfs -o rw,nosuid,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.109.0.189,mountvers=3,mountport=4046,mountproto=udp,local_lock=none,addr=10.109.0.189 bilbo.arrs.arrisi.com:/vol/users/users/lbrigman/private /users/lbrigman Note the above command is a single long line. On Mon, Jul 11, 2016 at 7:44 PM, John Jason Jordan <[email protected]> wrote: > On Mon, 11 Jul 2016 19:05:46 -0700 > Don Buchholz <[email protected]> dijo: > > > > >I think you're really close ... > > > >(1) > > sudo mount -t nfs > > 192.168.0.101:*/*volume1/Synology /media/jjj/Synology > > > > ... that little "/" in front of 'volume1' could be important. > > You may be onto something here. First, I thought the : was the proper > divider, and when I replaced it with the / I got something interesting > (see below). Then I added both, i.e., :/ and the command executed > without error. It's finally mounted!! > > But all is not completely well, because I can't > access /media/jjj/Synology. Here is what I did: > > sudo mount 192.168.0.101/volume1/Synology /media/jjj/Synology > mount: special device 192.168.0.101/volume1/Synology does not exist > > sudo mount 192.168.0.101:/volume1/Synology /media/jjj/Synology > <Hooray, no error messages!! <Note both : and /.> > > But all is not well: > cd /media/jjj/Synology/ > bash: cd: /media/jjj/Synology/: Permission denied > > ls -la > d--------- 26 root root 81920 Jul 10 18:38 Synology > > Aargh! Now the /media/jjj/Synology folder is owned by root again, the > same as happened when I mounted the share with SMB. Except this time > note all the missing permissions, which didn't happen when I mounted it > with SMB. > > I was able to change ownership to jjj with 'sudo chown,' which is > also different from the SMB experience. Mounted with SMB the folder was > owned by root and I was not able to take ownership, even after sudo su. > On the other hand I could see all the files and act on them, it's > just that they were all owned by the mysterious user 1026, thus rsync > was not able to transfer ownerships from the source files. > > I suppose I could also change the permissions here with chmod. But the > greater question is why is this even happening? > > In any event, thanks for the breakthrough insight! Finally a shred of > progress! > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
