[Bugs] [Bug 1293342] Data Tiering:Watermark:File continuously trying to demote itself but failing " [dht-rebalance.c:608:__dht_rebalance_create_dst_file] 0-wmrk-tier-dht: chown failed for //AP.BH.avi on wmrk-cold-dht (No such file or directory)"
bugzilla at redhat.com
bugzilla at redhat.com
Wed Dec 30 16:29:09 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1293342
--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13045 committed in release-3.7 by Dan
Lambright (dlambrig at redhat.com)
------
commit 7d84f8b95ecfa4f3d68eb0cbe7bd18f4293ec441
Author: Mohammed Rafi KC <rkavunga at redhat.com>
Date: Wed Dec 16 17:16:36 2015 +0530
tier: Demotion failed if the file was renamed when it was in cold
During migration if the file is present we just open the file
in hashed subvol. Now if the linkfile present on hashed is just
linkfile to another subvol, we actually open in hashed subvol.
But subsequent operation will go to linkto subvol ie,
to non-hashed subvol. This operation will get failed
since we haven't opened d on non-hashed.
Backport of>
>Change-Id: I9753ad3a48f0384c25509612ba76e7e10645add3
>BUG: 1292067
>Signed-off-by: Mohammed Rafi KC <rkavunga at redhat.com>
>Reviewed-on: http://review.gluster.org/12980
>Tested-by: NetBSD Build System <jenkins at build.gluster.org>
>Reviewed-by: Susant Palai <spalai at redhat.com>
>Tested-by: Gluster Build System <jenkins at build.gluster.com>
>Reviewed-by: Dan Lambright <dlambrig at redhat.com>
>Tested-by: Dan Lambright <dlambrig at redhat.com>
(cherry picked from commit d2f48214d436be633efb1136ee951b0736935143)
Change-Id: I562ac4ba73e6b572bc1be91e55a029fa75262b33
BUG: 1293342
Signed-off-by: Mohammed Rafi KC <rkavunga at redhat.com>
Reviewed-on: http://review.gluster.org/13045
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Reviewed-by: Dan Lambright <dlambrig at redhat.com>
Tested-by: Dan Lambright <dlambrig at redhat.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
More information about the Bugs
mailing list