Patch submitted upstream: http://review.gluster.org/#/c/9255/
Master URL: http://review.gluster.org/#/c/9255/ (IN REVIEW) Release 3.7 URL: http://review.gluster.org/#/c/13656/ (IN REVIEW)
Master URL: http://review.gluster.org/#/c/9255/ Release 3.7 URL: http://review.gluster.org/#/c/13656/ RHGS 3.1.3 URL: https://code.engineering.redhat.com/gerrit/#/c/70563/
Still seeing inode number for hard link file is different in USS on build glusterfs-3.7.9-1.el7rhgs.x86_64. Output from USS: ============================================ [root@dhcp46-47 snap1]# ls -ltrhi myfile 13005932563110049509 -rw-r--r--. 2 root root 13 Mar 29 23:52 myfile [root@dhcp46-47 snap1]# ls -ltrhi newfile 10093952695401965882 -rw-r--r--. 2 root root 13 Mar 29 23:52 newfile Output from snapshot: ============================================ [root@dhcp46-47 nfs]# ls -ltrhi newfile 13771270023539088487 -rw-r--r--. 2 root root 13 Mar 29 23:45 newfile [root@dhcp46-47 nfs]# ls -ltrhi myfile 13771270023539088487 -rw-r--r--. 2 root root 13 Mar 29 23:45 myfile Moving back to assigned state.
Hi Anil, Your test-case is wrong: Here is the test-case 1) create a file1 2) create a hard-link file2 3) create snapshot snap1 4) create snapshot snap2 Inside snap1 inode-number of file1 = inode-numer of file1 Please don't compare with inode number outside snap1 Thanks, Vijay
Failed QA because the build got spawned right before this patch got merged into the 3.1.3 branch. Moving it to POST.
Patch "https://code.engineering.redhat.com/gerrit/#/c/70563/" is merged
Hard link file have same inode number as source file. Bug verified on build glusterfs-3.7.9-2.el7rhgs.x86_64 Output from client [root@dhcp46-47 fuse]# ls -ai myfile 11820165462172882239 myfile [root@dhcp46-47 fuse]# ls -ai newfile 11820165462172882239 newfile Output from USS [root@dhcp46-47 snap1]# ls -i myfile 1667499072259270622 myfile [root@dhcp46-47 snap1]# ls -i newfile 1667499072259270622 newfile
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1240