similar to: NFS boot of Xen DomU - Goes to NFS version 2

Hello list, So I'm having a strange issue with Centos 7 mounting NFS V3. It starts with autofs. For example, my auto.share file: apps -nfsvers=3 some-server:/mnt/xfs1/& This will mount, but the first mount takes ~30 sec. After this, eventually the mount becomes stale but it still shows as connected in 'mount'. At this point, I can no longer mount NFS shares. Manual mounting

Hi all, Which ports do I need to have open on an NFS client's firewall to allow it to connect to a remote NFS servers? When I disable iptables (using ConfigServerFirewall), it connects fine, but as soon as I enable it, NFS gives me this error: root at saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to

Hello, We have a VM (under KVM - a VPS service by our ISP) running CentOS 7. On it we have 2 NFS mounts, one for backup and one as a live file system (where there are two user homes as well): ----------------------------------------------------------------------------------------------------------------------- # cat /etc/fstab /dev/mapper/centos-root / xfs defaults

I have been googling and searching the archive , haven''t got anything helpful. Would appreciate any help. Got the follow error when trying to start a domain using NFS root IP-Config: Incomplete network configuration information. Looking up port of RPC 100003/2 on 10.10.24.141 <http://10.10.24.141> RPC: sendmsg returned error 101 portmap: RPC call returned error 101 Root-NFS:

Hi All, I'm having an issue with connecting Gluster with NFS. When I do gluster volume status. It shows the ports aren't opened. NFS Server on localhost N/A N/A N N/A the /var/log/glusterfs/etc-glusterfs-glusterd.vol.log file states this: [2017-07-10 15:48:25.214618] I [MSGID: 106006] [glusterd-svc-mgmt.c:323:glusterd _svc_common_rpc_notify]

I'm having an interesting/odd problem with nfs (I think). We recently (Monday/Tuesday) upgraded our file server from an ancient redhat 7.3 system to a shiny new centos 6.4 system. We don't see any issues between the other centos boxes, but things get a bit weird when we start mounting on the old solaris clients. The initial symptom was that the 'tab complete' wasn't

On 2/6/2017 1:46 ??, Nikolaos Milas wrote: > After a bit of search, I found the associated reports: > > https://bugs.centos.org/view.php?id=13351 > https://bugzilla.redhat.com/show_bug.cgi?id=1454876 > > No solution yet, but -as a workaround- it seems that -at least- nfs > problems are indeed solved with downgrading. I have been working fine with CentOS 7.3, since I

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

We encountered a weird problem today, and I thought some of you might like to hear the solution. The underlying change was listed in the 7.4 changelog, so it's not a bug, but it may drive you buggy. The majority of our HPC cluster nodes run CentOS 7, though the exact patch levels vary from node to node. None is older than 7.3, but a few newer nodes were kickstarted right to 7.4. The

Hello everyone, I am using pxelinux to boot kernel from network, which goes ok. But when root must be mounted from NFS, I get the following code: Looking up port 100003/2 on 192.168.1.1 RPC: sendmsg returned error 22 portmap: RPC call returned error 22 ROOT-NFS: unable to get nfsd port number from server, using default looking up port of RPC 100005/1 on 192.168.1.1 RPC: sendmsg returned error

Hi This is a PXELinux problem that I'm facing. The problem, in brief, is that I have a set of diskless nodes (AMD Athlon XP 1800+ with 256MB RAM) connected via an internal 172.20.0.0/24 network to a dual AMD Opteron running SuSE Linux 8.3 for AMD64. I want the remote machines to diskless boot off the main server and run independently. The diskless machines have a PXE-compliant BIOS for

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

Our large and complex build system is having very sporadic failurs as we try to update to CentOS 4.5. This takes the form of files that exist - and have existed for some time - not being found: file.whatever: No such file: No such file or directory This happens both with source files, .o's - meaning that the errors come from both the compiler and linker. The build storage is on NFS and the

We have a 2-node Oracle RAC that keeps getting the following error: kernel: nfs: RPC call returned error 88 The storage being mounted is netapp. We 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:

Commit-ID: c4b811a1e4647224ddc717fac59900d16d0e9d4d Gitweb: http://git.kernel.org/?p=libs/klibc/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

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 NFSv4 at present). If both

I have been trying to boot Xen guest (Fedora Core 6 - linux version 2.6.18) from NFS server but I kept encountering a problem despite using ramdisk or not. Key items in my config file are as follows: ================================================= kernel = "/root/Xen/xen-3.1.0-src/linux-2.6.18-xenU2/vmlinuz" # Optional ramdisk. # ramdisk = "/boot/initrd-2.6.18-xenU2.img"

After getting a reasonably configured NFS4 setup working on my Scientific Linux server, I spent a majority of my evening trying to do the same with my Centos 5 box, with fruitless results. Most attempts to mount that server returns the following message: [root at sl01 log]# mount -t nfs4 192.168.15.200:/opt/company_data /mnt mount.nfs4: Operation not permitted As nearest as I can tell, I was

I''ve locked up my dom0 a couple of times this morning copying a 3GB file from local disk to an NFS mount(neither xend nor guests running). I don''t encounter this problem on the stock CentOS 4 kernel. The machine is a PowerEdge 2850 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