search for: nfsver

...c/klibc.git;a=commit;h=c4b811a1e4647224ddc717fac59900d16d0e9d4d Author: Baptiste Jonglez <baptiste.jonglez at imag.fr> AuthorDate: Thu, 14 Sep 2017 09:22:21 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] nfsmount: support nfsvers= and vers= options The standard mount option nowadays to specify NFS version is "nfsvers", as documented in nfs(5) on modern Linux systems. Up to now, nfsmount only supported the old "v2" or "v3" boolean options. Extend option parsing to support both "nfsvers=...

The standard mount option nowadays to specify NFS version is "nfsvers", as documented in nfs(5) on modern Linux systems. Up to now, nfsmount only supported the old "v2" or "v3" boolean options. Extend option parsing to support both "nfsvers=X" and "vers=X", with X being equal to either 2 or 3 (nfsmount does not support...

...changed. While NFS v4.0 was the default up to 7.3, the 7.4 protocols are subtly different: 1. Try NFS v4.1 first 2. Fail down to NFS v3 3. Fail down to NFS v2 The problem is that our Isilon works with NFS v4.0, not 4.1, but 4.0 is not in the fail-down path. The short-term answer is to specify nfsvers=4.0 in our autofs configuration files, which works like a charm. Like I said, this was an announced change, but the implications escaped us until now. So this little writeup is just for the record. -- Paul Heinlein heinlein at madboa.com 45?38' N, 122?6' W

.../dev/mapper/centos-root / xfs defaults 0 0 UUID=7a3ae70a-8ef3-463b-8f5b-be4e2e7be894 /boot xfs defaults 0 0 /dev/mapper/centos-swap swap swap defaults 0 0 10.201.40.34:/data/col1/noc-bkups-1 /mnt/dd2500-1 nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 10.201.40.34:/data/col1/hesperia-mount /hesperiamount nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 ----------------------------------------------------------------------------------------------------------------------- This setup has been working f...

...t_squash,sync,insecure) exportfs -rv on bigdog: (client) mkdir /tmp/test/b1 /tmp/test/b2 /tmp/test/g1 /tmp/test/g2 touch /tmp/test/b1/nothing_is_mounted /tmp/test/b2/nothing_is_mounted /tmp/test/g1/nothing_is_mounted /tmp/test/g2/nothing_is_mounted mount -F nfs -o nfsvers=3 boltzmann:/summit_bolt /tmp/test/b1 mount -F nfs -o nfsvers=3 boltzmann:/scrs1_bolt /tmp/test/b2 mount -F nfs -o nfsvers=3 goblin:/summit.mirror /tmp/test/g1 mount -F nfs -o nfsvers=3 goblin:/scrs1.mirror /tmp/test/g2 ls -l /tmp/test/* -rw-r--r-- 1 root...

...with 2 e1000 cards - the one in use is connected to a PowerConnect 2216 10/100 switch and has negotiated 100Mbit. I''ll check if the stock Cambridge isn''t negotiating full duplex but that shouldn''t cause lockups. My mount options are: defaults,intr,rsize=32768,wsize=32768,nfsvers=3,tcp,timeo=600 This isn''t at NetApp (no 100Mbit there), but these are the options used by all their linux NFS clients. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...the storage - CentOS 6.4 also built-in drivers (Linux stor1.colocat.ru 2.6.32-279.el6.x86_64). On the storage is made an array, that is shown in system as /storage/s01. Then it is exported via NFS. The nodes connect to NFS by: /bin/mount -t nfs -o rdma,port=20049,rw,hard,timeo=600,retrans=5,async,nfsvers=3,intr 192.168.1.1:/storage/s01 /home/storage/sata/01 mount shows: 192.168.1.1:/storage/s01 on /home/storage/sata/01 type nfs (rw,rdma,port=20049,hard,timeo=600,retrans=5,nfsvers=3,intr,addr=192.168.1.1) Then we create a virtual machine with virsh with a disk bus virtio. All is OK, until we don...

...s: server 10.201.40.34 not responding, still trying ... ----------------------------------------------------------------------------------------- I tried downgrading to rpcbind-0.2.0-38.el7.x86_64 but this time it didn't help. I mount either directly: ? mount -vv -o auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 -t nfs 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2 or through /etc/fstab: ? 10.201.40.34:/data/col1/hesperia-mount?? /hesperiamount2?? nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 The box may even hung during reboot, which has never happened...

Hi! Did anyone encountered problems with nfs after the latest updates? I started to have problems like nfsvers=3 no longer working in fstab or messages like : RPC: Program not registered Thanks! Adrian

On 07/01/2015 11:51 AM, Tru Huynh wrote: > On Wed, Jul 01, 2015 at 11:36:36AM +0300, Adrian Sevcenco wrote: >> Hi! Did anyone encountered problems with nfs after the latest updates? >> I started to have problems like nfsvers=3 no longer working in fstab >> or messages like : >> RPC: Program not registered > at work, our diskless warewulf setup is still working fine here > NFS client running 2.6.32-504.23.4.el6.x86_64 hmm, nice that you mentioned that! i was on kernel-ml 4.0.4 got back on rhel/centos...

...se diskless machines needs its own hostname. Presently my pxelinux.cfg is setup like: prompt 1 default Gentoo timeout 10 label Gentoo kernel boot/kernel-3.16.5-gentoo APPEND root=/dev/nfs rw ip=dhcp nfsroot=192.168.1.10:/RAID/diskless/XXXXX-mythtv-0.27-fixes,tcp,rsize=131072 ,wsize=131072,nfsvers=3 Where the XXXXX is the hostname. Because I have 3 of these machines I am using up 3 times the disk space. I am wondering if there is a way all 3 of them can run from the same nfsroot, but somehow have different hostnames/machine-ids. Presently the hostname comes from /RAID/diskless/XXXXX -myt...

...t / xfs defaults 0 0 UUID=297e2939-d6f5-431a-9813-9848368ee306 /boot xfs defaults 0 0 /dev/mapper/centos-swap swap swap defaults 0 0 10.201.40.34:/data/col1/noc-bkups-1 /mnt/dd2500-1 nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 Any other ideas? Thanks, Nick

On 22/9/2017 2:58 ??, Nikolaos Milas wrote: > ... > or through /etc/fstab: > > ? 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2?? nfs > auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 Correction: the /etc/fstab nfs mount line has one more zero: ? 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2?? nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 I am looking forward to your feedback. Based on the facts and experience, it looks...

...120,acdirmax=120,hard,nocto,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.19.19.19,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=10.19.19.19) cat /etc/fstab storage:/vmail??? /vmail??? nfs??? rw,sec=sys,noexec,noatime,tcp,hard,rsize=65536,wsize=65536,intr,nordirplus,nfsvers=3,tcp,actimeo=120,nocto??? 0??? 0 Probably somthing in kernel or mount options. Any idea ?

...build storage is on NFS and the errors don't happen when we target local disk. We also have solaris nad Centos 3.x building the same code base in a similar fashion with no problem. We are currently using mount options of: rw,nosuid,bg,timeo=50,retry=1 And have also tried: rw,intr,bg,proto=tcp,nfsvers=3,rsize=32768,wsize=32768 without success. Any suggestions welcome. -Mark

...don't see any errors/issues on the storage itself or the switches this client is connecting thru. The NFS network is a 2-interface ( 2 x 1Gb UTP) bond which shows no errors of any kind. We are mounting with the following mount options: rw,noac,nointr,bg,hard,timeo= 600,wsize=32768,rsize=32768,nfsvers=3,tcp This problem sometimes hits the OCR votedisk shares and causes the instance to crash. These systems were upgraded to 5.6 back in January. Currently running 2.6.32-300.4.1. Thanks for any info,

...onization of his mailbox again. The Dovecot version and configuration is the same that in CentOS 6, also the mount parameters are the same, so I suspect that could be some difference in the NFS client implementation on CentOS 7. This the entry on fstab: 192.168.1.2:/vmail0 /mnt/vmail0 nfs rw,nfsvers=3,noatime,nodiratime,_netdev,nordirplus??? 0??? 0 # Bind for vmail0 /mnt/vmail0/domains /home/vmail/domains none x-systemd.requires=/mnt/vmail0,x-systemd.automount,bind 0 0 In the archive of this list I found a similar issue but without a solutions: https://dovecot.org/pipermail/dovecot/2018-Oc...

...gt; mount point on the same client that the native client has mounted the > volume. The client refuses with the error: > > mount -t nfs bs1:/gl /mnt/glnfs > mount: bs1:/gl failed, reason given by server: No such file or > directory > Harry, Have you tried: # mount -t nfs -o nfsvers=3,tcp bs1:/gl /mnt/glnfs Also, there is an /etc/sysconfig/nfs file that may let you remove RDMA as a mount option for NFS.

...ied mounting ext3 with -o reservation and switch to NFS over TCP, with no improvement. Both systems are Centos 5.2 with kernel 2.6.18-92.1.22.el5 The ext3 is mounted with rw,nosuid,nodev,usrquota,grpquota,acl NFS export: rw,sync,no_root_squash 8 NFS threads. Remotely mounted with options rw,intr,nfsvers=3,proto=udp,rsize=32768,wsize=32768 I would be very grateful for any help. Andrzej

On 2/6/2017 10:40 ??, Philippe BOURDEU d'AGUERRE wrote: > Reverting to rpcbind-0.2.0-38.el7 solves the problem for me Thank you very much Philippe, I notice that I have upgraded to rpcbind-0.2.0-38.el7_3.x86_64 on May 26. Have you checked if this bug/behavior has been reported or should we file a bug report? Nick