similar to: I stream read - stale NFS file handle (reboot of server)

If you export two subvolumes of a btrfs filesystem, they will both be given the same uuid so lookups will be confused. blkid cannot differentiate the two, so we must use the fsid from statfs64 to identify the filesystem. We cannot tell if blkid or statfs is best without knowing internal details of the filesystem in question, so we need to encode specific knowledge of btrfs in mountd. This is

NFS needs a unique identifier for a filesystem to be able to export it. This can be set by the admin (fsid= in /etc/exports) but that is a hassle and it is best to set it automatically. nfs-utils currently uses the UUID returned by libblkid if that works, or the fsid returned by statfs64 if libblkid finds nothings and fsid is non-zero. Otherwise it uses device major/minor. This

[ adding klibc ml to cc ] On Thu, Feb 01, 2007 at 09:29:52AM -0600, John Goerzen wrote: > > It appears to be largely undocumented, but a review of > /usr/share/initramfs/scripts/nfs shows that this package supports NFSv2 > and v3 only. I don't know why v4 isn't supported. yup, this needs nfs v4 support in klibc nfsmount. would be could to get that soon postetch, but someone

Hi folks, I have a Centos 6 NFS server, which dirves me crazy. The directory I try to export cant be accessed by different clients. I tried a centos 7, centos 6 and a pool of vmware esxi 5.5 systems. At the client side I get errors like: mount.nfs: Stale file handle or Sysinfo set operation VSI_MODULE_NODE_mount failed with the tatus Unable to query remote mount point's attributes. On

I''m seeing some pretty pitiful performance using ZFS on a NFS server, with a ZFS volume exported (only with rw=host.foo.com,root=host.foo.com opts) and mounted on a Linux host running kernel 2.4.31. This linux kernel I''m working with is limited in that I can only do NFSv2 mounts... irregardless of that aspect, I''m sure something''s amiss. I mounted the zfs-based

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 have a requirement to run NFS read-only in an Internet-facing colocation environment. I am not happy with packet filters alone around rpcbind, call me paranoid, so I just spent the last few minutes cutting this patch. As you are aware, RPC applications can be forced to listen on a known port through the sin/sa argument to bindresvport[_sa](). Why several Linux distributions have this

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

Hi all, I've been making a wrapper script for the backup tool 'duplicity', allowing me to create config files for each resource, wherein I define whether a snapshot should be made prior to backing up the resource or not. Now I find that my snapshots never change .... The script creates a snapshot, creates md device, mounts it, runs backup against the mounted snapshot,

is it possible to set up NFS on centos 5.5 so that it uses *only* version 4? i tried this not that long ago on fedora and was surprised to see a complaint when i tried to start the server and was told that i was missing required functionality of NFSv1, or something equally weird. i'll check the /etc/init.d/nfs script, but i think what got me into trouble was trying to use the entire set of

I have seen some talk about this but have not seen any answers. I know this is a problem on CentOS 7.1 and I also think it is a problem on CentOS 7.0. Basically if I have an NFS client only config - meaning that the nfs-server.service is not enabled then I have to wait 60 seconds after boot for the 1st NFSV3 mount to succeed. What I can surmise is the following. I attempt to perform a NFS

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 see that the built-in NFS support registers mountd in portmap only with tcp and not udp. While this makes sense for a TCP-only NFS implementation, it does cause problems for some clients: Ubuntu 10.04 and 7.04 mount just fine. Ubuntu 8.04 gives "requested NFS version or transport protocol is not supported", unless you specify "-o mountproto=tcp" as a mount option, in

I run chkrootkit daily. For the first time I've got reports of a problem - Checking `bindshell'... INFECTED (PORTS: 1008) The page http://fatpenguinblog.com/scott-rippee/checking-bindshell-infected- ports-1008/ suggests that this might be a false positive, so I ran 'netstat - tanup' but unlike the report, it wasn't famd on the port. It was tcp 0 0 0.0.0.0:1008

Hello, I am upgrading to the current R 2.5.1 under Sun Solaris 8. I call the configure script with the --without-readline flag, and it works fine. Then, when I invoke make, I get this kind of error messages: make[2]: Entering directory `/usr/local/R/R-2.5.1-inst/src/library' >>> Building/Updating help pages for package 'base' Formats: text html latex example

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.

Hi I've suddenly lost access to some permanent cross-server shares. I think this was following the Nov 5 new kernel, rather than the Centos version upgrade. I don't see any difference to man mount.nfs I have:- [root at hs6 ~]# mount hs8:/data /sysback/hs8-data -v mount: no type was given - I'll assume nfs because of the colon mount: trying 172.26.0.8 prog 100003 vers 3 prot tcp port

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"

Hello, I am moving LDAP from one domain to another We have moved off of a.wustl.edu network to b.school.edu network. I have searched vi /etc/nslcd.conf vi /etc/openldap/ldap.conf and removed all referances to "a" I restarted /etc/init.d/nscd restart this is redhat 6.7, and my ldap server is now ldap.b.wustl.edu:389 a.school.edu to b.school.edu I keep getting messages

hi, i trying to install a fai installation server in a DomU for DomUs, but i have some problems with nfs. The DomUs says, that they can''t reach the NFS Server =========== Begin: Retrying nfs mount ... IP-Config: eth0 hardware address 00:16:3e:7a:25:7c mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.16.0.255 IP-Config: eth0 complete (from 172.16.0.151): address: