similar to: Update to EL 6.3 breaks TCP NFS automounts

Hi, I'm trying to setup a firewalled NFS server. I've configured my server (CentOS 5) using the following parameters /etc/sysconfig/nfs MOUNTD_NFS_V1="no" MOUNTD_NFS_V2="no" RQUOTAD_PORT=875 LOCKD_TCPPORT=32803 LOCKD_UDPPORT=32769 RPCNFSDCOUNT=64 MOUNTD_PORT=892 STATD_PORT=662 STATD_OUTGOING_PORT=2020 SECURE_NFS="yes" modprobe.conf: options lockd

Hi all, 1) My NFS3 clients don't display or obey existing non-POSIX ACLs on files of NFS3-mounted exports. 2) setfacl on the client throws error and fails : # setfacl -m u:stowler:rw testfile.text setfacl: testfile.text: Operation not supported 3) at time of client mount the server's /var/log/messages shows "kernel: svc: unknown version (3)". Any thoughts greatly

Hi all, I have setup a CentOS6.3 x86_64 host to act as a nfs server. According to RHEL6 docs, portmap is not needed when you use NFSv4, but in my host I need to start rpcbind service to make NFSv4 works. My /etc/sysconfig/nfs # # Define which protocol versions mountd # will advertise. The values are "no" or "yes" # with yes being the default MOUNTD_NFS_V2="no"

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 have changed /etc/sysconfig/nfs to specify port numbers for NFS daemons. Somehow statd is still starting up at random port number. Other damons are starting at properly at specified port numbers Any clues on what might be wrong? Any other location/setting that takes precedence over sysconfig/nfs ? It's CentOS 5.5 64bit with nfs-utils 1.0.9-44.el5. -- Thanks, CS

The in-kernel nfsroot code is obsoleted by kinit. Remove it; it causes conflicts. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 161e1dc16ec1129b30b634a2a8dcbbd1937800c5 tree c30da837d746fe65d8a13ccf6f27bd381948edb4 parent 018604e070e143657abcf0cb256a1e2dda205d97 author H. Peter Anvin <hpa at zytor.com> Sat, 20 May 2006 16:24:05 -0700 committer H. Peter Anvin <hpa at

This removes the appliance configuration bits from the installer and associated files since it has been deprecated --- installer/modules/ovirt/files/cobbler-import | 6 - .../modules/ovirt/files/ovirt-appliance-setup | 4 - installer/modules/ovirt/files/ovirt-storage | 73 ---------- installer/modules/ovirt/manifests/appliance.pp | 152 -------------------- 4 files

after this latest centos 5 kernel update, i am seeing 40 second delays on automount points. nothing in the rpm changelog looks obviously related to autofs and the autofs module seems to be the same as the previous kernel. i'm starting to do some strace'ing and other debugging, but nothing has jumped out at me yet. i'm hoping someone else has seen it so i know i'm not alone

hi guys in my qutest I have this: ...     <filesystem type='mount' accessmode='passthrough'>       <source dir='/home'/>       <target dir='/home'/>     </filesystem> ... and on the host /home/* are user home dirs which are automounted off a glusterfs volume. The guest starts okey, I can see dirs under /home but if I go to /home/userA I

On Mon, Jun 10, 2019 at 12:28:02PM +0100, lejeczek wrote: > hi guys > > in my qutest I have this: > > ... > >     <filesystem type='mount' accessmode='passthrough'> >       <source dir='/home'/> >       <target dir='/home'/> >     </filesystem> > > ... > > and on the host /home/* are user home

Below is my firewall rules for iptables. everything is working fine except for NFS I cannot mount my drive. If I turn off iptables I can mount. Looking at this : http://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-nfs.html Important In order for NFS to work with a default installation of Red Hat Enterprise Linux with a firewall enabled, IPTables with the default TCP port 2049

Greetings, I installed RedHat Linux AS version 3/Update 3 over the weekend, along with ocfs RPMs that are listed below: ocfs-2.4.21-EL-smp-1.0.13-1.i686.rpm ocfs-support-1.0.10-1.i386.rpm ocfs-tools-1.0.10-1.i386.rpm Oracle 10g was then installed on the systems. On both the test cluster that I used and the production cluster that I installed over the weekend are some pretty strange lines

Hi, I am configuring firewall for NFS. I see that statd and mountd start at random port. Is there any way to force it to start at specific port each time. The '-p ' option would work, but how do I configure it to start at specific port number each time. I mean where do statd and mountd look for default configuration options? Any clues? - CS.

I'm trying to NFS-mount a CentOS directory on my Fedora laptop, but I find I can only do this is I turn off the firewall on the CentOS server. If instead I go to system-config-securitylevel-tui on the server, and allow NFS4, this does not do the trick. Nor does allowing port 2049. What do I need to allow? [I should say that the CentOS server is remote, and difficult to access directly; that

Hi Folks, I'm using VMWare on a Linux Host (CentOS) with a Linux-Guest Sidux). And I'd like to use NFS. Furthermore I'd like to use the Firewall in CentOS with this little GUI. If I activate this firewall then my Guest says "no route to host" on mounting nfs. Firewall disabled -> no problem occurs. Is there a solution to use firewall _and_ nfs ? Please, no iptables

An embedded message was scrubbed... From: Niki Kovacs <contact at kikinovak.net> Subject: Re: [CentOS] Getting started with NFS Date: Sat, 04 Jul 2009 10:33:31 +0200 Size: 1377 URL: <http://lists.centos.org/pipermail/centos/attachments/20090704/b8ff2d37/attachment-0003.eml>

I've got a newly installed Centos 5.0 box, planned to replace an ageing server (solaris box). I've set up the nfs shares, but the other solaris boxes won't mount them, unless I turn of iptables on the Centos box. If I do that, they mount, and all operations tested to date work fine. Iptables is allowing the 2049 tcp and udp ports already. What else needs to be opened up in

Hi, What is the magic juju that I have to put in /etc/sysconfig/autofs to get autofs to default to using NFSv4, rather than NFSv3, for mounting file systems? I don't want to place these flags into the automount maps themselves because we have a varied network with Sun, CentOS, RedHat and Macintosh systems, and the flags that have to get added to automount maps (which we distribute centrally

Hello everyone, I am setting up a new system for use as a testing/demo/trial-and-error system. I have installed CentOS 4.4 on it. There is not an X-environment, so I will need to fix this from the command line (via ssh access). I am trying to do an nfs export from this box to another on my internal home network. I have figured out that it is a firewall issue on the CentOS box (I turn off the

On 11/20/20 2:31 PM, Michael B Allen wrote: > On Fri, Nov 20, 2020 at 2:06 PM Michael B Allen <ioplex at gmail.com> wrote: >> Apparently I don't know how to do "that" because this: >> >> # iptables -A INPUT -p tcp --sport 760 -m conntrack --ctstate >> NEW,ESTABLISHED -j ACCEPT >> >> still doesn't allow the traffic through (not that I