first time here posting, i hope i won't do many mistakes.
I've a setup with 2 NFS server. They're using corosync/pacemaker + drbd to offer active/passive nfs server. Distro used is Ubuntu latest LTS version.
Cluster is also offering a floating ip for clients to connect. Volume replication works fine.
The problem is that during the failover the i/o operations wait for approx 90 seconds. After failover (with the new machine already promoted as new master) tcpdump on the client shows packets like:
reply ok 52 getattr ERROR: unk 10013
Looking for Error 10013 and nfs on google leaded me to this usenet post
So my locks are retained to the nfs server and only after 90 sec they're freed. I need to lower that parameter (contained in /proc) but when i try
root@nfs-ha-1:/# ls -l /proc/fs/nfsd/nfsv4gracetime -rw------- 1 root root 0 Jan 31 11:00 /proc/fs/nfsd/nfsv4gracetime root@nfs-ha-1:/# cat /proc/fs/nfsd/nfsv4gracetime 90 root@nfs-ha-1:/# echo 1 > /proc/fs/nfsd/nfsv4gracetime bash: echo: write error: Device or resource busy root@nfs-ha-1:/#
So i'm need of further info about this issue, or a way to write on that file. The files are created at run time with nfs-server. If i stop the nfsserver they directory is simply empty, and i cannot write to it.
root@nfs-ha-1:/proc/fs/nfsd# touch nfsv4gracetime touch: cannot touch `nfsv4gracetime': No such file or directory