The client that does work is halfway around the globe going through some IPSec tunnels on a ATT MPLS circuit. NFS server and boxes that don’t work are on the same exact switch (albeit different VLAN but same exact router/switch). The disk is formatted and mounted in OMV, I enabled NFS, shared the folder (named 'Nascal') with all users (read/write).
#Ubuntu setup nfs share install#
Other clients write 1GB+ files fine with kerberos enabled. I was able to install and setup open media vault on my rasberry pi 2b through ssh but Im not able to access the folder I created. The confusing part to me is that it only happens on certain boxes. What I am speculating is happening is happening is that the NFS server or client isn’t responding to some ack or something to validate the close of the connection so it just hangs indefinitely.
During its switch from A to B the server released the lock. However, I don’t know why I did it, but while the client was locked up, I restarted the NFS server to make it move from Controller A to Controller B on the Dell Unity box. Turned Kerberos back on mounted the shares again, try it again, same issue. Does it at 700MB/s+ (10Gbps network) on the problem clients. A client can be a remote system, a Virtual Machine on the same server or the server itself. I disabled kerberos on the NFS server on the dell unity box, no issues with writes for 20GB files. Now that we’re done with NFS server configurations, the remaining part is mounting NFS shares on a client system. Which at face value seems to work.however what i’ve noticed is that these problem clients won’t finish their writes/close. Go through the config, point it to your ldap server, your KDC, DNS server, create your share and done. However, what I think I have found out is it’s something to do with kerberos (no fucking surprise). You can see one is completing the other isn’t after the files get to a certain size. This is showing dd results of two clients to the same exact NFS. Top is on the failing clients, bottom is on a client that works. After reboot, mount the nfs share, and again can move around and do stuff until I try writing a file of any size.Ĭentos/RHEL clients don’t have a problem. In /etc/exports, add the following line where directory is the directory you would. I’ve tried killing the process and it won’t die doing kill -9. 500MB binary file) or use something like dd, the command will never finish. I can even touch a file and that’s successful. I can ls, cd, look around with ls without issues. The NFS share server is a Dell EMC unit box.Īpt-get install nfs-common nfs-kernel-serverįor whatever reason without the nfs-kernel-server package installed Ubuntu won’t even mount the nfs share when krb5 is used. So to be short, cp, dd both lock up on Ubuntu machines (NFS clients) when copying any amount of data to the NFS share we have setup when using krb5.
0 kommentar(er)
