Hi Matt I have noticed rgw file rename is not POSIX strictly, because src file and dest file own different inode number (hash of bucket + object).I have not tested on nfs-ganesha upstream for some reason, and will checkout to master to test FSAL_RGW later. For NFS scaling, the main problem is that different NFS-ganesha server keep its inode cache in local memory and there is no global view of inode cache(directory tree) in the NFS-ganesha cluster connectted to the same rgw bucket. For I have tested NFS-ganesha HA with pacemaker+corosync wachted and found inode cache cannot be shared between primary and backup. For NFSv4, session state and lock state should be persist to storage, so the NFS-ganesha cluster can share them. In addition, what is the plan of flock in rgw file, for it is important to NFS cluster. Chen Min -----邮件原件----- 发件人: Matt Benjamin [mailto:mbenjamin@xxxxxxxxxx] 发送时间: 2016年9月9日 22:17 收件人: 陈敏 <chenmin@xxxxxxxx> 抄送: The Sacred Order of the Squid Cybernetic <ceph-devel@xxxxxxxxxxxxxxx> 主题: rename PR 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 ��.n��������+%������w��{.n����z��u���ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
