Hi all, I am trying to set up a highly available NFS server, using Heartbeat and DRBD on Debian Etch. Everything works great, except for one thing. File locking does not seem to work well when using an IP alias or secondary IP address for the NFS resource. When a NFS client is waiting for a lock to be released, it isn't notified by the server when the file becomes free. After 30 seconds the client asks the server again about the lock status, and only then the client knows the lock is free (so, almost 30 seconds too late). When I use a primary IP address for the NFS resource I don't have this problem.
I have really searched several days for more information about this problem, I also filed a Debian kernel bug report (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447562). This is not a Heartbeat problem at all, but I would like to know if anyone else has encountered this problem. Is this a Debian specific problem? A solution for me would be to use a primary IP address on an extra NIC instead of an alias or secondary address. But afaik IPaddr and IPaddr2 can't do this. Is there a standard script to accomplish this? Thanks a lot, Mark _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
