Hi Chen, I wanted to let you know, I merged your exact-match PR. Now, I suspect that you're also not running a recent-enough version of nfs-ganesha, because I think that the rename issue you fixed wouldn't easily reproduce if you were. A key point I wanted to highlight is that it's part of the scaling (and ha, and...) strategy that our nfs file handles are name-stable, rather than arbitrary values. One implication of that is that when a file is renamed, the renamed object has a different file id and hence NFS file handle value than it did before the rename. We use the parent directory's change attribute to ensure that clients that had the vnode cached see an invalidate. (Nothing in your PR contradicts that, of course.) Another strategic decision we made is, we don't rename directories (just stating it for posterity). :) Cheers, Matt -- Matt Benjamin Red Hat, Inc. 315 West Huron Street, Suite 140A Ann Arbor, Michigan 48103 http://www.redhat.com/en/technologies/storage tel. 734-707-0660 fax. 734-769-8938 cel. 734-216-5309 -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
