Hi! I'm wondering: Does "unlock" mean that all file locks are invalidated? If so, I think it's a bad idea, because for a migration of the NFS server the exports will be stopped/started, thus loosing all locks. That's not what a HA NFS-Server should do. HA NFS-Servers try hard to preserve locks.
Regards, Ulrich Windl >>> Kristoffer Grönlund<[email protected]> schrieb am 11.03.2014 um 11:37 in Nachricht <20140311113711.2bf52a63@ultralix>: > Hi, > > I have created a submit request for the NFS exportfs agent to change > the default for the parameter unlock_on_stop from 0 to 1. > > The resource agent should really release all locks which the NFS server > holds when stopping the resource. When this option was introduced, the > default was kept as 0 for compatibility reasons with legacy kernels, > existing users and non-Linux systems. > > There has been a bit of discussion in the submit request whether > changing the default makes sense, and right now things are leaning > towards making the change. [1] > > Are there any objections from anyone else? > > [1]: https://github.com/ClusterLabs/resource-agents/pull/394 > > Thanks, > > -- > // Kristoffer Grönlund > // [email protected] > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
