search for: root_squash

...he first host and the second host and the third, or if it is because my first host is defined by IP, and the second two are define by hostname. But the cause is likely one or the other. hostnames and ips are omitted, but you should get the idea. *%cat /etc/exports * /gpfs/nfs/share n.n.n.n(rw,root_squash,fsid=nnn) n.n.n.n(rw,root_squash,fsid=nnn) n.n.n.n(rw,root_squash,fsid=nnn) *%showmount -e nnnn* Export list for nnnn: /gpfs/nfs/share n.n.n.n *%exportfs -r* *%showmount -e nnnn* Export list for nnnn: /gpfs/nfs/share n.n.n.n, n.n.n.n, n.n.n.n regards, Charles

...AM, TomK wrote: > Hey Martin, > > Thanks very much. Appreciate you jumping in on this thread. Can you provide some more details with respect to which libvirt version you have installed. I know I've made changes in this space in more recent versions (not the most recent). I'm no root_squash expert, but I was the last to change things in the space so that makes me partially fluent ;-) in NFS/root_squash speak. Using root_squash is very "finicky" (to say the least)... It wasn't really clear from what you posted how you are attempting to reference things. Does the "/v...

...e: >>> Hey All, >>> >>> I've an issue where libvirtd tries to access an NFS mount but errors >>> out with: can't canonicalize path '/var/lib/one//datastores/0 . The >>> unprevilidged user is able to read/write fine to the share. >>> root_squash is used and for security reasons no_root_squash cannot be >>> used. >>> >>> On the controller and node SELinux is disabled. >>> >>> [oneadmin@mdskvm-p01 ~]$ virsh -d 1 --connect qemu:///system create >>> /var/lib/one//datastores/0/38/deployment....

.... My test case is : root at wagram:~# swaks --to tstifi04 --server imap --protocol lmtp --header-X-Spam-Status yes root at wagram:~# (imap VM LMTP proxies to telegraphe5 VM in this test) mbox folders are in users homedir, no generic "vmail" unix account. Real posixAccounts in LDAP, NFS root_squashed. sieve "fileinto "Junk" call goes wrong : > Feb? 6 17:56:03 telegraphe5 dovecot: lmtp(tstifi04): Error: > PytSHqIRW1x2dgAA+Fldtw: sieve: msgid=unspecified: failed to store into > mailbox 'Junk': Read-only mbox straced : https://pastebin.com/A53hDYnS I may miss...

...C3 that worked. On the server, I have the following data structure: /data /data/archive /data/pictures /data/music Each is a separate ext3 filesystem mounted with rw,acl. /etc/exports presents all of these filesystems properly: # exportfs -v /data/pictures 172.17.17.0/27 (rw,wdelay,insecure,root_squash,no_subtree_check,anonuid=65534,anongid=65534) /data/archive 172.17.17.0/27 (rw,wdelay,insecure,root_squash,no_subtree_check,anonuid=65534,anongid=65534) /data/music 172.17.17.0/27 (rw,wdelay,insecure,root_squash,no_subtree_check,anonuid=65534,anongid=65534) /data 172.17.17.0/27 (rw,...

...Hey Martin, >> >> Thanks very much. Appreciate you jumping in on this thread. > Can you provide some more details with respect to which libvirt version > you have installed. I know I've made changes in this space in more > recent versions (not the most recent). I'm no root_squash expert, but I > was the last to change things in the space so that makes me partially > fluent ;-) in NFS/root_squash speak. > > Using root_squash is very "finicky" (to say the least)... It wasn't > really clear from what you posted how you are attempting to reference &...

...;> >>> Thanks very much. Appreciate you jumping in on this thread. >> Can you provide some more details with respect to which libvirt version >> you have installed. I know I've made changes in this space in more >> recent versions (not the most recent). I'm no root_squash expert, but I >> was the last to change things in the space so that makes me partially >> fluent ;-) in NFS/root_squash speak. >> I'm always lost in how do we handle *all* the corner cases that are not even used anywhere at all, but care about the conditions we have in the co...

...s very much. Appreciate you jumping in on this thread. >>>> Can you provide some more details with respect to which libvirt version >>>> you have installed. I know I've made changes in this space in more >>>> recent versions (not the most recent). I'm no root_squash expert, but I >>>> was the last to change things in the space so that makes me partially >>>> fluent ;-) in NFS/root_squash speak. >>>> >> >> I'm always lost in how do we handle *all* the corner cases that are not >> even used anywhere at al...

...not due to rdns, but by the fact that: > > > > Ok this part, check again after the reboot, i forget the -v > for the exportfs... ( sorry ) > > exportfs -v > > Now i've: > > root at vdmpp1:~# exportfs -v > /home > 10.27.0.0/21(rw,wdelay,root_squash,no_subtree_check,sec=sys:kr > b5,rw,secure,root_squash,no_all_squash) > > but i've had sec=krb5 only, so... O;-))) Ok, so sys works, this confirms a problem with detecting the nfs spns. > > > > Remove the one with NFS. > > OK. But server is in production, so.....

...ogwatch tells me /nfs4exports/Data1 and /Data1 have same filehandle for *,192.168.0.0/24,192.168.0.0/255.255.255.0, using first The tutorial I was following suggested making a root connection as ro, then the data connections as rw, so I have /nfs4exports 192.168.0.0/24 (ro,sync,insecure,root_squash,no_subtree_check,fsid=0) /nfs4exports/Data1 192.168.0.0/24(rw,insecure,no_subtree_check,nohide) /nfs4exports/home 192.168.0.0/24(rw,insecure,no_subtree_check,nohide) However, when I ls nfs4exports I get Data1 home which ties in, I think, with the logwatch report. Can someone please explain...

I have been running a local repository on a CentOS4 server. It serves CentOS4 clients (and FC5, FC6, and SuSE10.x if I bother to mention). My current options for exports is (ro,wdelay,insecure,root_squash). The ro and insecure options were added manually and others are default. I understand 'sync' is the default although it is not shown by exportfs -v. I also found this description in the NFS FAQ: "For the Linux implementation of NFS Version 3, using the "async" export opti...

...ound the sun. On 4/7/2016 7:32 PM, TomK wrote: > Hey All, > > I've an issue where libvirtd tries to access an NFS mount but errors > out with: can't canonicalize path '/var/lib/one//datastores/0 . The > unprevilidged user is able to read/write fine to the share. > root_squash is used and for security reasons no_root_squash cannot be > used. > > On the controller and node SELinux is disabled. > > [oneadmin@mdskvm-p01 ~]$ virsh -d 1 --connect qemu:///system create > /var/lib/one//datastores/0/38/deployment.0 > create: file(optdata): /var/lib/one//da...

...Appreciate you jumping in on this thread. >>>>> Can you provide some more details with respect to which libvirt version >>>>> you have installed. I know I've made changes in this space in more >>>>> recent versions (not the most recent). I'm no root_squash expert, but I >>>>> was the last to change things in the space so that makes me partially >>>>> fluent ;-) in NFS/root_squash speak. >>>>> >>> I'm always lost in how do we handle *all* the corner cases that are not >>> even used any...

...the freezes do not happen. Now I have tried many different nfs server options and other nfs client options. I also set up a test nfs server with centos4 and 5 where I am the only user, and while copying big chunks of date, nfs freezes (hangs) too. Here is my /etc/exports: /home *domain.com(rw,root_squash,sync,no_subtree_check,no_wdelay) Here is how client workstations mount the export in the fstab fshome:/home /home/ nfs rsize=8192,wsize=8192,intr 0 0 Am I mis-configuring the nfs server of clients? Is there anything I am not doing right? If anybody has any suggestions, I would appreciate...

.../export/users # In /etc/fstab add localhost:/users /export/users glusterfs defaults,_netdev 0 0 mount /export/users 4. Export the gluster mounted volume from the gluster server using CentOS 5.5 provided NFS server: cat /etc/exports /exports/users/someuser 192.168.2.10(rw,async,root_squash) 5. Start system provided NFS server on the gluster server, configure the firewall properly for NFS access 6. On the client machine, 192.168.2.10, check that the export is advertised: $ /usr/sbin/showmount -e nas-srv-01 Export list for nas-srv-01: /export/users/someuser 192.168.2.10 7. Mount it...

...come unresponsive. In fact, the entire client becomes unresponsive, essentially making them unusable until samba is restarted. We first saw this and connected it to the following open bug in samba (https://bugzilla.samba.org/show_bug.cgi?id=11720). However, after mitigating the issue by removing root_squash from the nfs mount, things stabilized for awhile, but we still see this symptom occur occasionally. One reproducible way to trigger it was to try and use the network drive as the user library install location in R/Rstudio. After informing all users not to do that, things seemed to stabilize again...

...eady doable, solves all the issues. > > > > So AIUI there are a few problems with this (although I'm still > > investigating and trying to make a local reproducer): > > > > - The external large space may be on NFS, with the usual problems > > there like root_squash, no SELinux labels, slowness. This means > > it's not suitable for the appliance, but might nevertheless be > > suitable for overlay files. > > If that is the only big storage space attached to a container, I do > not see any alternative than use it, with all the ca...

Hai Marco, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Gaiarin via samba > Verzonden: vrijdag 26 oktober 2018 11:23 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Again NFSv4 and Kerberos at the 'samba way'... > > Mandi! L.P.H. van Belle via samba > In chel di` si favelave... > >

...as my proposal IIRC) which you would point to the NFS > mount. /var/tmp would be local storage, and used for the appliance. > (There are other ways to do this if for some reason /var/tmp must be NFS.) Or: (3) set LIBGUESTFS_CACHEDIR away from /var/tmp or NFS-mounted places, so we avoid any root_squash issue, and avoid any sharing of temporary files that linger after the container execution. -- Pino Toscano

Hi everyone, If a VM is configured to have a console attached to it, like using http://libvirt.org/formatdomain.html#elementCharConsole Libvirt offers access to VM serial console's using the virDomainOpenConsole API[1] However, I didn't find a way to 1. list the existing connections to the console 2. kill an existing connection - without reconnecting using VIR_DOMAIN_CONSOLE_FORCE[2]