From 6c54022f1b1c7f5f458f6a7e783203d11e7f89b5 Mon Sep 17 00:00:00 2001 From: shishir gowda Date: Thu, 5 Jan 2012 15:38:32 +0530 Subject: cluster/dht: handle ENOENT err in rename fop A ENOENT should not be a error propogated for rename failures. As, ENOENT can arise only due to internal unlink call of rename. Change-Id: I925622da8ef370d0385bc5b30cf8dc9b8e852beb BUG: 768879 Signed-off-by: shishir gowda Reviewed-on: http://review.gluster.com/2583 Tested-by: Gluster Build System Reviewed-by: Amar Tumballi Reviewed-by: Anand Avati --- xlators/cluster/dht/src/dht-rename.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'xlators/cluster/dht') diff --git a/xlators/cluster/dht/src/dht-rename.c b/xlators/cluster/dht/src/dht-rename.c index 02b12887f67..fa06de71175 100644 --- a/xlators/cluster/dht/src/dht-rename.c +++ b/xlators/cluster/dht/src/dht-rename.c @@ -646,7 +646,8 @@ dht_rename_links_cbk (call_frame_t *frame, void *cookie, xlator_t *this, "link/file on %s failed (%s)", prev->this->name, strerror (op_errno)); local->op_ret = -1; - local->op_errno = op_errno; + if (op_errno != ENOENT) + local->op_errno = op_errno; } this_call_cnt = dht_frame_return (frame); -- cgit