search for: rootsquash

...oot squash via an NFS pool is "easy" (famous last >>>> words) >>>> >>>> Create some pool XML (taking the example I have) >>>> >>>> % cat nfs.xml >>>> <pool type='netfs'> >>>> <name>rootsquash</name> >>>> <source> >>>> <host name='localhost'/> >>>> <dir path='/home/bzs/rootsquash/nfs'/> >>>> <format type='nfs'/> >>>> </source> >&g...

...n 4/12/2016 5:08 PM, John Ferlan wrote: >> Having/using a root squash via an NFS pool is "easy" (famous last words) >> >> Create some pool XML (taking the example I have) >> >> % cat nfs.xml >> <pool type='netfs'> >> <name>rootsquash</name> >> <source> >> <host name='localhost'/> >> <dir path='/home/bzs/rootsquash/nfs'/> >> <format type='nfs'/> >> </source> >> <target> >>...

..."easy" (famous last >>>>> words) >>>>> >>>>> Create some pool XML (taking the example I have) >>>>> >>>>> % cat nfs.xml >>>>> <pool type='netfs'> >>>>> <name>rootsquash</name> >>>>> <source> >>>>> <host name='localhost'/> >>>>> <dir path='/home/bzs/rootsquash/nfs'/> >>>>> <format type='nfs'/> >>>>>...

...lib/one//datastores/0/38/deployment.0|grep -i nfs >>> [oneadmin@mdskvm-p01 ~]$ >>> Having/using a root squash via an NFS pool is "easy" (famous last words) Create some pool XML (taking the example I have) % cat nfs.xml <pool type='netfs'> <name>rootsquash</name> <source> <host name='localhost'/> <dir path='/home/bzs/rootsquash/nfs'/> <format type='nfs'/> </source> <target> <path>/tmp/netfs-rootsquash-pool</path> <permi...

...p -i nfs >>>> [oneadmin@mdskvm-p01 ~]$ >>>> > Having/using a root squash via an NFS pool is "easy" (famous last words) > > Create some pool XML (taking the example I have) > > % cat nfs.xml > <pool type='netfs'> > <name>rootsquash</name> > <source> > <host name='localhost'/> > <dir path='/home/bzs/rootsquash/nfs'/> > <format type='nfs'/> > </source> > <target> > <path>/tmp/netfs-root...

[ I would be way easier to reply if you didn't top-post ] On Tue, Apr 12, 2016 at 12:07:50PM -0400, TomK wrote: >Hey John, > >Hehe, I got the right guy then. Very nice! And very good ideas but I >may need more time to reread and try them out later tonight. I'm fully >in agreement about providing more details. Can't be accurate in a >diagnosis if there isn't

...er that does not support SMB. I wish to mount this directory on a second system and re-export it via samba so that users can access their unix home directories from their windows boxes. My samba server is running CentOS 5.0, and I have the the home directories mounted at /home/na, and there is no rootsquash, so the root user on my server has full access to the home directoris. My smb.conf is below: [global] workgroup = UNIXPEOPLE server string = smbserver # logs split per machine # max 50KB per log file, then rotate security = user passdb backend = tdbs...

...this to "just" be a FS file, then it won't necessarily know to try to access the file properly (OK dependent upon libvirt version too perhaps - the details have been paged out of my memory while I do other work). One other thing that popped out at me: My /etc/exports has: /home/bzs/rootsquash/nfs *(rw,sync,root_squash) which only differs from yours by the 'no_subtree_check' your environment though seems to have much more "depth" than mine. That is you have "//datastores/0/38/disk.1" appended on as the (I assume) disk to use. The question then becomes - does...

On Mon, Apr 11, 2016 at 08:02:04PM -0400, TomK wrote: >Hey All, > >Wondering if anyone had any suggestions on this topic? > The only thing I can come up with is: '/var/lib/one//datastores/0/38/disk.1': Permission denied ... that don't have access to that file. Could you elaborate on that? I think it's either: a) you are running the domain as root or b) we

...n it won't necessarily know to > try to access the file properly (OK dependent upon libvirt version too > perhaps - the details have been paged out of my memory while I do other > work). > > One other thing that popped out at me: > > My /etc/exports has: > > /home/bzs/rootsquash/nfs *(rw,sync,root_squash) > > which only differs from yours by the 'no_subtree_check' > > your environment though seems to have much more "depth" than mine. That > is you have "//datastores/0/38/disk.1" appended on as the (I assume) > disk to use. The...