On March 17, 2020 10:21:53 PM GMT+02:00, Shareef Jalloq <[email protected]> wrote: >Hi all, > >I'm trying to set up a hosted engine on an NFS share provided by a >Synology >NAS. I've been reading the info and threads regarding the requirement >that >the share be owned by vdsm:kvm with uid:gid of 36:36, but this seems >impossible to set on modern Synology boxes. > >My understanding of DSM is that the user doesn't have control of the >UID >and GID of users. You can ssh in and modify /etc/passwd but these >files >are auto-generated from Synology's own scripts so changes here will not >persist across reboots. Is that correct? > >Secondly, having read lots of posts about permissions and various >issues >around export settings, why isn't this documented anywhere? There just >seems to be lots of contradictory posts. For example, my experience >has >been: > > - my Synology vdsm:kvm ids are 1028:65536 > - the permissions on the NFS export are 777, anything else gives >permissions errors in HE setup > - the hosted engine install went fine with these settings. >- the nfs-check.py script provided to check the NFS export fails but >the >installation still completes. > >So are these issues specific to Synology or is the documentation out >there >just wrong? > >#confused > >Cheers, Shareef.
Actually, I have seen users using anonuid=36,anonguid=36,all_squash (or whatever were the anon user options) which forces all users on the share to be mapped to nfsnobody and that user/group will have uid of '36'. It's worth checking the Sinology documentation. Best Regards, Strahil Nikolov _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/OETROOEAFC7KXSRW5YVDFUR3ATTZOPOU/
