diff options
author | Saravanakumar Arumugam <sarumuga@redhat.com> | 2016-01-22 16:58:13 +0530 |
---|---|---|
committer | Vijay Bellur <vbellur@redhat.com> | 2016-03-07 19:13:20 -0800 |
commit | 478203fd9447cbc67c7cdc2980d6bdf4881984bf (patch) | |
tree | cd1b2ef07b42f03614702ef360e1df13fc142289 /geo-replication/syncdaemon/libcxattr.py | |
parent | e2f644b8d0ad3f729bfbae1322b6f3940fac8138 (diff) |
geo-rep: Handle hardlink in Tiering based volume
Problem:
Hardlinks are synced as Sticky bit files to Slave in
a Tiering based volume.
In a Tiering based volume, cold tier is hashed subvolume
and geo-rep captures all namespace operations in cold tier.
While syncing a file and its corresponding hardlink, it is
recorded as MKNOD in cold tier(for both) and
We end up creating two different files in Slave.
Solution:
If MKNOD with Sticky bit set is present, record it as LINK.
This way it will create a HARDLINK if source file exists (on slave),
else it will create a new file.
This way, Slave can create Hardlink file itself (instead
of creating a new file) in case of hardlink.
Change-Id: Ic50dc6e64df9ed01799c30539a33daace0abe6d4
BUG: 1302979
Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
Signed-off-by: Aravinda VK <avishwan@redhat.com>
Reviewed-on: http://review.gluster.org/13281
Reviewed-on: http://review.gluster.org/13315
Smoke: Gluster Build System <jenkins@build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Diffstat (limited to 'geo-replication/syncdaemon/libcxattr.py')
0 files changed, 0 insertions, 0 deletions