Tag Info

New answers tagged

0

@tigran - thank you for the help. You raised some very important points. The problem here was actually port numbers. In the first scenario: Device 172.16.50.100 (static)]----[Gateway (172.16.15.200)]----[Ubuntu Linux Server 172.16.10.100] The device was requesting: authenticated mount request from 172.16.50.100:709 ...


0

I'm assuming this is at a hosting provider? The simple answer is it depends on their policy, but generally you would only pay for the 1Gb once when it leaves Apache, not when it leaves the NFS server. Most hosting providers only charge for data when it passes through their router, so traffic between two machines at the same provider is free. If you want ...


0

I ended up solving the problem. It turns out that adding new machines to the switch had nothing to do with it. The same day that we added those machines, one of the users created a single huge file (~260GB). NFS was stalling out copying that file. My solution was to add --max-size=100G to the rsync command in rsnapshot. This means that one large file ...


0

# /etc/init.d/nfs start FATAL: Module nfsd not found. FATAL: Error running install command for nfsd ... It is actually harmless, you don't need to do anything. In case you want this to go away, uncomment (or add) the line NFSD_MODULE="noload" in /etc/sysconfig/nfs file.


2

AFAIK there is no user authentication support for NFS using credentials. The authentication is based on the source IP address of the NFS client (ie: the ESXi host) and the actual mount point. Maybe you mean Samba Shares (aka windows shares)? Those are not supported on ESXi. Only NFS and iSCSI are supported.


0

To use POSIX ACLs with NFS, you had to use NFSv3. NFSv4 ACLs are way different that POSIX ACLs. The first one are set using the very specific nfs4_getacl and nfs4_setacl, while the latter are configured with the standard getfacl/setfacl binaries. In short, NFSv4 ACLs have nothing to do with POSIX ACLs (they are much more similar to the CIFS ACLs used in ...


0

It is save to restart NFA server. The clients will reestablish the mounts. Restarting NFS services on the client must be save as well, as this is limited to user space processes only, without unmounting. But check with OS.


0

You must use getfacl on the NFS server (because you query the local file-system), and use nfs4_getfacl when you are on the NFS client. NFSv4 ACL and Linux ACL acl(5) are completely different standard ! The Linux NFS server will translate the ACL back and forth. Read the post No acl on nfs mount in RHEL6?.


1

The ACL are used and active over NFS. Use the command nfs4_getfacl to show the ACL on an NFSv4 mount: $ nfs4_getfacl /tmp/test A::OWNER@:rwatTnNcCy A::alice@nfsdomain.org:rxtncy A::bob@nfsdomain.org:rwadtTnNcCy A:g:GROUP@:rtncy D:g:GROUP@:waxTC A::EVERYONE@:rtncy D::EVERYONE@:waxTC The reason why the ACL look so different compared to Linux ACL? Because ...


0

If you are mounting a network drive that will be slow. Use rsync -aud from windows to linux it will take less than 1 minute after the first run for many TB (assuming neg monthy changes). If you want versioning use rdiff-backup after the rsync. Other options; http://en.m.wikipedia.org/wiki/List_of_backup_software


0

My guess would be that the problem is caused by the use of fsid=0 in one of your exports. Remember that the fsid is meant to uniquely identify devices when the underlying filesystem driver doesn't provide its own unique IDs. And in particular, fsid=0 has a special meaning: For NFSv4, there is a distinguished filesystem which is the root of all exported ...



Top 50 recent answers are included