summaryrefslogtreecommitdiffstats
path: root/xlators/cluster/dht/src/dht-common.c
diff options
context:
space:
mode:
authorManikandan Selvaganesh <mselvaga@redhat.com>2015-02-02 11:57:54 +0530
committerVijay Bellur <vbellur@redhat.com>2015-04-02 03:21:08 -0700
commit1d6cd6bb0f2f5875e8e4ad370cf1ff2c601cbfd4 (patch)
treeee33c0da18965079b2c95de1dfa3c794be7539f7 /xlators/cluster/dht/src/dht-common.c
parent12e603bb9d8bc220eeea01c0ecc8ca63f9df4bc4 (diff)
Xlators : Fixed typos
Change-Id: I948f85cb369206ee8ce8b8cd5e48cae9adb971c9 BUG: 1075417 Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com> Reviewed-on: http://review.gluster.org/9529 Reviewed-by: Niels de Vos <ndevos@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com> Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
Diffstat (limited to 'xlators/cluster/dht/src/dht-common.c')
-rw-r--r--xlators/cluster/dht/src/dht-common.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/xlators/cluster/dht/src/dht-common.c b/xlators/cluster/dht/src/dht-common.c
index b7df1f4da4b..9a98ebfab30 100644
--- a/xlators/cluster/dht/src/dht-common.c
+++ b/xlators/cluster/dht/src/dht-common.c
@@ -989,7 +989,7 @@ dht_lookup_unlink_of_false_linkto_cbk (call_frame_t *frame, void *cookie,
*lookup_everywhere and one where unlink-failed. So
*at this point in time we cannot decide which one to
*choose because there are chances of first cached
- *file is truncated after rebalance and if it is choosen
+ *file is truncated after rebalance and if it is chosen
*as cached node, application will fail. So return EIO.*/
if (op_errno == EBUSY) {
@@ -1150,7 +1150,7 @@ dht_lookup_everywhere_done (call_frame_t *frame, xlator_t *this)
* If this lookup is performed by rebalance and this
* rebalance process detected hashed file and by
* the time it sends the lookup request to cached node,
- * file got migrated and now at intial hashed_node,
+ * file got migrated and now at initial hashed_node,
* final migrated file is present. With current logic,
* because this process fails to find the cached_node,
* it will unlink the file at initial hashed_node.