search for: no_root_squash

...s (rw) /dev/sde1 on /working type xfs (rw,nobarrier) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) nfsd on /proc/fs/nfsd type nfsd (rw) /dev/drbd0 on /newwing type xfs (rw) Here is /etc/exports on the server, /data 10.10.10.0/24(rw,no_root_squash,async) /data 10.10.11.0/24(rw,no_root_squash,async) /data 150.x.x.192/27(rw,no_root_squash,async) /data 150.x.x.64/26(rw,no_root_squash,async) /home 10.10.10.0/24(rw,no_root_squash,async) /home 10.10.11.0/24(rw,no_root_squash,async) /opt 10.10.10.0/24(rw,no_root_squash,async) /opt...

...ta /nfsexport/data none bind 0 0 ---8<--- AS you can see, /mnt/data is a partition mounted below /. I am binding both partitions to /nfsexport/... and export them in /etc/exports with ---8<---/etc/exports--- / server*.pamas.local(ro,secure,no_root_squash,crossmnt,fsid=0) /mnt/data server2.pamas.local(ro,secure,no_root_squash,nohide) server5.pamas.local(ro,secure,no_root_squash,nohide) ---8<--- If I execute [root at server5 ~]# /etc/init.d/nfs reload I get exportfs: /mnt/data does not support NFS export exportfs: /mnt/data does not supp...

...dd("exports") do setcode do case Facter.hostname when (/thishost/i): [ "/local", "/local2" ] end end end & a template like this: <% exports.each do |exp| -%> <%= exp %> 155.198.204.0/255.255.255.0(rw,sync,no_root_squash) <% end -%> When I test the fact locally, the output is exports: /local/local2 (although ''facter exports'' gives /local and /local2 on separate lines). When Puppet runs and uses the template, the line output is /local/local2 155.198.204.0/255.255.255.0(rw,sync,no_root_sq...

...RBD 0.6.12 heartbeat-1.0.4-2.fr.c.1.um.2 The new CentOS mailstores and all their clients are running... kernel 2.6.9-22.0.1.ELsmp nfs-utils-1.0.6-65.EL4 DRBD 0.7.14 heartbeat-1.2.3.cvs.20050927-1.centos4 Qmailrocks 2.2.0 /etc/exports on the mailstores contains... /mnt/drbd/ mailserv1(rw,sync,no_root_squash) /mnt/drbd/ mailserv2(rw,sync,no_root_squash) /mnt/drbd/ mailserv3(rw,sync,no_root_squash) /mnt/drbd/ mailserv4(rw,sync,no_root_squash) And the NFS mounts on the client mailservers look like... mailstore1:/mnt/drbd/home /home nfs defaults 0 0 If anyone's seen this or can shed...

...8.1.152 number = 2 name = st02 cluster = ocfs2 cluster: node_count = 2 name = ocfs2 --- cat /etc/exports # /etc/exports: the access control list for filesystems which may be exported # to NFS clients. See exports(5). /snfs 192.168.1.0/24(rw,sync,no_root_squash,no_subtree_check,fsid=0) /snfs/projects 192.168.1.0/24(rw,sync,no_root_squash,no_subtree_check) /snfs/configs 192.168.1.0/24(rw,sync,no_root_squash,no_subtree_check) /snfs/variables 192.168.1.0/24(rw,sync,no_root_squash,no_subtree_check) /snfs/backups 192.168.1....

I have been experimenting exporting btrfs subvolumes over nfs. Main subvolume is filesys1 mounted at /filesys1. Below this is subvolume base, user1 is in base and documents is in user1. documents is mounted at /documents. /etc/exports is: /filesys1/base/user1 172.16.0.0/24(rw,no_acl,no_root_squash,fsid=0) /filesys1/user1-snapshot 172.16.0.0/24(rw,no_acl,no_root_squash,fsid=0) /documents 172.16.0.0/24(rw,no_acl,no_root_squash,fsid=0) On the client machine I mount user1 as /mnt/user and all data from user is present. I can also umount /mnt/usr and mount /documents as /mnt/document...

...gt;> client. I did minimal setup on the Centos machine. >>> >>> Hi Rowland, >>> >>> The problem wasn't getting NFS to work - it was getting NFS "root" >>> access to work between a CentOS 7 client and CentOS 7 server? (AKA >>> no_root_squash in /etc/exports). >>> >>> Finally, after a significant amount of effort, I figured that out >>> last night. >>> >>> In my case, I needed to add a realms section for realm >>> AD.EECS.YORKU.CA and include 2 auth_to_local rules as follows: >&...

Hello, I am running an NFS server/PXE on a Cent OS 5.1 server. I have defined an NFS export with "no_root_squash" option in my /etc/exports file: # # NFS Export Files # /export/images *(rw,sync,no_root_squash) ... A client PXE boots as a diskless station to the above server into a root-NFS directory underneath the above /export/images export. When the client boots; the NFS export is NO...

...http://pastebin.com/f6ff5890a I tried the same script on an USB-HDD and it works fine, even for / Here are some information about the NFS config: cat /proc/mounts | grep nfs: http://pastebin.com/f250c9f63 (I aslo tried bigger rsize and wsize) exportfs -v: /volume1 192.168.0.13(rw,wdelay,no_root_squash,no_subtree_check) cat /var/lib/nfs/etab: /volume1 192.168.0.13(rw,sync,wdelay,hide,nocrossmnt,secure,no_root_squash,no_all_squash,no_subtree_check,secure_locks,acl,anonuid=65534,anongid=65534) cat /var/lib/nfs/xtab: /volume1 molungus(rw,sync,wdelay,hide,nocrossmnt,secure,no_root_s...

...ning CentOS51 and is configured per PXE/Syslinux and RHEL diskless workstation documentation. 1. Attempt to test ability for client to PXE boot over the network and run Root-NFS 2. NFS export in the PXE server is: # # NFS Export Files for qatest1 host # /export/images *(rw,sync,no_root_squash) /tftpboot *(rw,sync,no_root_squash) Note - We want the client to mount the export - with "no_root_squash" .. it is for a test environment hence we would like to have the client root possess effective ROOT permission. 3. Client boots successfully via PXE and mounts the Ro...

...and a Centos 7 Unix domain member as the NFS client. I >> did minimal setup on the Centos machine. > > Hi Rowland, > > The problem wasn't getting NFS to work - it was getting NFS "root" > access to work between a CentOS 7 client and CentOS 7 server? (AKA > no_root_squash in /etc/exports). > > Finally, after a significant amount of effort, I figured that out last > night. > > In my case, I needed to add a realms section for realm > AD.EECS.YORKU.CA and include 2 auth_to_local rules as follows: > > [realms] > ? AD.EECS.YORKU.CA = { > ?...

...static IP address to - I have enabled NFS on the server. I tried using Knoppix and Gentoo Live on the diskless node, and tried remote mounting. It works perfectly and flawlessly. The contents of /etc/exports have been, at different points in time, one of these: /tftpboot/remote 172.20.0.11(rw,no_root_squash) /tftpboot/remote 172.20.0.12(rw,no_root_squash) /tftpboot/remote 172.20.0.13(rw,no_root_squash) or /tftpboot/remote 172.20.0.0/24(rw,no_root_squash) or /tftpboot/remote 172.20.0.0/255.255.255.0(rw,no_root_squash) or /tftpboot/remote (rw,no_root_squash) but have made no differ...

I used to have an exports file like the following on redhat 7.3... the would allow any machine to mount the /home/CentOS.iso directory. /var/spool/lpd (rw) /etc/silentm slave(ro,secure,no_all_squash,no_root_squash) /home/CentOS.iso (ro,secure,no_all_squash,no_root_squash) This does not seem to work on centos 4.2. I have to explicitly have a machine name like: /home/CentOS.iso machine(ro,secure,no_all_squash,no_root_squash) for it to mount. I have been looking at the nfs man page and dont see why this is...

I have been trying all sorts of things to get this working. nfsv4 works fine if I just use the nfs-v3 form of export i.e. /nfs4exports 192.168.230.237/24(ro,fsid=0,sync,insecure,no_root_squash,no_subtree_check,squash_uids=0-99) /nfs4exports/NDG 192.168.230.237/24(rw,insecure,no_subtree_check,nohide,sync,no_root_squash,squash_uids=0-99) but this is inherently open to all on this machine. so then using this recipe http://www.techrepublic.com/blog/opensource/kerberos-authentication-with-n...

...he fsid=0 argument in my /etc/exports file. That gives me a whole different error [root at pebble-anoop ~]# mount -v -t nfs4 pebble-anoop:/test/ /mnt/ mount: pinging: prog 100003 vers 4 prot tcp port 2049 mount: special device pebble-anoop:/test/ does not exist Also, the parameter root_squash or no_root_squash don't make any difference whatsoever. Any ideas how I can solve this? It is imperative that I use NFSv4. NFSv3 won't do. Thanks. -anoop

...em on centos 5.8 kernel and nfs4. On server i have bind mounted directory shared to the client with following setup: mounted directory: /srv/nfs/imagetest on /exports/imagetest type none (rw,bind) /etc/exports file: /exports 10.0.4.0/24(ro,insecure,sync,wdelay,no_subtree_check,no_root_squash,fsid=0,crossmnt) /exports/imagetest 10.0.4.20(rw,insecure,sync,wdelay,no_subtree_check,nohide,no_root_squash) On client I have mounted it with following command: 10.0.4.2:/ on /media/nfs type nfs4 (rw,nodev,sync,proto=tcp,retry=10,rsize=32768,wsize=32768,hard,intr,addr=10.0.4.2) This...

Hi Dear List, i am experiencing strange problem with NFS, they is CentOS 6.2 x86_64 machines. One CentOS is sharing two directories (following) /etc 192.168.0.41(rw,sync,no_root_squash) /var/named/master 192.168.0.41(rw,sync,no_root_squash) nfs is started on server side there are proper entries in fstab at client side for both shares. however server is able to mount "/etc" alright but not "/var/named/master" any idea ? why that. Thanks Nath

Hi. I have Samba AD configured correctly, and can mount kerberized NFS from all the CentOS 7 clients.? I'm not able to use "root" on the client even though the nfs export specifies the option: no_root_squash option. I completely understand that in order to use the "root" identity (which doesn't exist as a user in the domain) on the NFS client, this identity has to be mapped to somewhere else.? That's why my samba config specifies a file for "username map" which contains:...

...member as the NFS client. >>> I did minimal setup on the Centos machine. >> >> Hi Rowland, >> >> The problem wasn't getting NFS to work - it was getting NFS "root" >> access to work between a CentOS 7 client and CentOS 7 server? (AKA >> no_root_squash in /etc/exports). >> >> Finally, after a significant amount of effort, I figured that out >> last night. >> >> In my case, I needed to add a realms section for realm >> AD.EECS.YORKU.CA and include 2 auth_to_local rules as follows: >> >> [realms] &g...

...memory = 128 name = "sarge-nfs" dhcp="dhcp" root = "/dev/nfs" nfs_server = ''10.10.24.141 <http://10.10.24.141>'' nfs_root=''/nfsroot'' extra = "2" /etc/exports on NFS server ************************* /nfsroot *(rw,sync,no_root_squash) rpcinfo -p output on NFS server program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100021 1 udp 1090 nlockmgr 100021 3 udp 1090 nlockmgr 100021 4 udp 1090 nlockmgr 100021 1 tcp 10...