Description of problem: the inode numbers are different for same file over nfs and fuse mounts Version-Release number of selected component (if applicable): 3.3.0qa25 How reproducible: always Steps to Reproduce: 1.create nfs and fuse mount 2.create a file 3. Actual results: the inode number is different Expected results: this bug filed to find the cause of the difference is their , as at present we think that the inode number should be same. Additional info:
@saurabh, Why do you think it is a glusterd issue?
[root@supernova ~]# stat /mnt/glusterfs/abcd /mnt/nfs/abcd File: `/mnt/glusterfs/abcd' Size: 6 Blocks: 16 IO Block: 131072 regular file Device: 22h/34d Inode: 10022916903501265893 Links: 8 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Context: system_u:object_r:fusefs_t:s0 Access: 2012-03-12 17:52:09.000000000 +0530 Modify: 2012-03-09 12:40:31.000000000 +0530 Change: 2012-03-12 17:37:50.000000000 +0530 Birth: - File: `/mnt/nfs/abcd' Size: 6 Blocks: 16 IO Block: 65536 regular file Device: 27h/39d Inode: 16535937926376003723 Links: 8 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Context: system_u:object_r:nfs_t:s0 Access: 2012-03-12 17:52:09.000000000 +0530 Modify: 2012-03-09 12:40:31.000000000 +0530 Change: 2012-03-12 17:37:50.000000000 +0530 Birth: - [root@supernova ~]# printf "0x%x 0x%x\n" 10022916903501265893 16535937926376003723 0x8b188dd1ee737be5 0xe57b73eed18d188b [root@supernova ~]# getfattr -d -m . -e hex /tmp/export/a3/abcd trusted.gfid=0xa04489d70f1946618b188dd1ee737be5 Some where in the code, we have a reverse logic of setting the inode numbers :-)
Amar, that still doesn't explain why it is a glusterd issue?
It is not. Hence I had moved the component to 'core' earlier itself.
CHANGE: http://review.gluster.com/2923 (nfs: no need to recalculate the 'ino' from gfid) merged in master by Vijay Bellur (vijay)