path: root/xlators/features/qemu-block
diff options
authorSaravanakumar Arumugam <>2015-06-09 17:49:58 +0530
committerRaghavendra G <>2015-06-11 22:26:16 -0700
commit27bcffc6b698b1ef16ef02a61109897e38faa54d (patch)
treedfca40faf5909cf1ebbf45ab5745248deed1c4f0 /xlators/features/qemu-block
parentf823a0cf796957b450521d731d37be7af09951ec (diff)
features/changelog: Avoid setattr fop logging during rename
Problem: When a file is renamed and the (renamed)file's Hashing falls into a different brick, DHT creates a special file(linkto file) in the brick(Hashed subvolume) and carries out setattr operation on that file. Currently, Changelog records this(setattr) operation in Hashed subvolume. glusterfind in turn records this operation as MODIFY operation. So, there is a NEW entry in Cached subvolume and MODIFY entry in Hashed subvolume for the same file. Solution: Avoid logging setattr operation carried out, by marking the operation as internal fop using xdata. In changelog translator, check whether setattr is set as internal fop and skip accordingly. Change-Id: I21b09afb5a638b88a4ccb822442216680b7b74fd BUG: 1230687 Signed-off-by: Saravanakumar Arumugam <> Reviewed-on: Tested-by: Gluster Build System <> Tested-by: NetBSD Build System <> Reviewed-by: Raghavendra G <> Tested-by: Raghavendra G <>
Diffstat (limited to 'xlators/features/qemu-block')
0 files changed, 0 insertions, 0 deletions