REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from an inode num and snapshot gfid) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from an inode num and snapshot gfid) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from an inode num and snapshot gfid) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from an inode num and snapshot gfid) posted (#4) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from an inode num and snapshot gfid) posted (#5) for review on master by Vijaikumar Mallikarjuna (vmallika)
Hi Vijai, I see this bug added as a known issue in the known issues tracker bug(1153907) for the 3.0.3 release. Can you please change the doc type to known issue and add the doc text?
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from an inode num and snapshot gfid) posted (#6) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from an inode num and snapshot gfid) posted (#7) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from snapname and gfid) posted (#8) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from snapname and gfid) posted (#9) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from snapname and gfid) posted (#10) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from snapname and gfid) posted (#11) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from snapname and gfid) posted (#12) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from snapname and gfid) posted (#13) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from snapname and gfid) posted (#14) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/9255 (uss/gluster: generate gfid for snapshot files from snapname and gfid) posted (#15) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/9255 committed in master by Rajesh Joseph (rjoseph) ------ commit e0f71288d95469d7ae82473ef273c6ba43250a36 Author: vmallika <vmallika> Date: Wed Feb 10 06:39:22 2016 +0530 uss/gluster: generate gfid for snapshot files from snapname and gfid If 'a' and 'b' are hardlinks, we need to generate a virtual gfid for these files so that the inode number for 'a' and 'b' are same. Generate gfid as below: gfid_of_a = MD5(snapname + back_end_gfid(a)) if '/dir1/a' and '/dir2/b' are hardlinks, then inode number should be same for all below files: /mnt/.snaps/snap1/dir1/a /mnt/.snaps/snap1/dir2/b /mnt/dir1/.snaps/snap1/a /mnt/dir2/.snaps/snap1/b Change-Id: Ifda793455610e554f3f1e4cbb90d44c02cda4b0f BUG: 1171703 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/9255 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Rajesh Joseph <rjoseph>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user