Hi David- On 04/09/2010 03:40 PM, David Teigland wrote:
Here's what I think was the first time we discussed cancelation and Bruce's provisional locks: http://marc.info/?t=116538335700005&r=1&w=2 I'm still skeptical of trying to handle cancels, it seems too complex to become reliable in the lifetime of nfs3. What I would be interested to see fixed is this oops that's not difficult to trigger by doing lock/unlock loops on a client: https://bugzilla.redhat.com/show_bug.cgi?id=502977#c18 But, for all the kernel work on these nfs/gfs/dlm hooks, there's a larger issue that no one is working on AFAIK: the mechanisms for recovering client locks on remaining gfs nodes when one gfs node fails. That would take a lot of work, and until it's done all the kernel apis will be a moot point since clustered nfs locks on gfs will be unusable.
To support IPv6, I've studied and modified the NFSv2/v3 lock recovery mechanisms quite a bit recently. What kernel APIs do you think would be needed to manage cluster lock recovery? Just something to release stale locks on a single node?
-- chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
