summaryrefslogtreecommitdiffstats
path: root/xlators/cluster/dht/src/dht-rebalance.c
diff options
context:
space:
mode:
authorYaniv Kaul <ykaul@redhat.com>2018-07-16 17:03:17 +0300
committerAmar Tumballi <amarts@redhat.com>2018-07-22 14:40:16 +0000
commit621138ce763eda8270d0a4f6d7209fd50ada8787 (patch)
tree7299759993f6e9f7f34dad95fc8d8cd6ffc1b2fd /xlators/cluster/dht/src/dht-rebalance.c
parentc0e76377d0fc47aa66f35ea70a4793731ebbd40c (diff)
All: run codespell on the code and fix issues.
Please review, it's not always just the comments that were fixed. I've had to revert of course all calls to creat() that were changed to create() ... Only compile-tested! Change-Id: I7d02e82d9766e272a7fd9cc68e51901d69e5aab5 updates: bz#1193929 Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
Diffstat (limited to 'xlators/cluster/dht/src/dht-rebalance.c')
-rw-r--r--xlators/cluster/dht/src/dht-rebalance.c12
1 files changed, 6 insertions, 6 deletions
diff --git a/xlators/cluster/dht/src/dht-rebalance.c b/xlators/cluster/dht/src/dht-rebalance.c
index 3b986be97e0..1f1beb8dca3 100644
--- a/xlators/cluster/dht/src/dht-rebalance.c
+++ b/xlators/cluster/dht/src/dht-rebalance.c
@@ -815,7 +815,7 @@ __dht_rebalance_create_dst_file (xlator_t *this, xlator_t *to, xlator_t *from,
*server (posix_layer) and binding it in server (incrementing fd count),
*so if in that time-gap, if other process sends unlink considering it
*as a linkto file, because inode->fd count will be 0, so file will be
- *unlinked at the backend. And because furthur operations are performed
+ *unlinked at the backend. And because further operations are performed
*on fd, so though migration will be done but will end with no file
*at the backend.
*/
@@ -1017,9 +1017,9 @@ __dht_check_free_space (xlator_t *this, xlator_t *to, xlator_t *from,
During rebalance `migrate-data` - Destination subvol experiences
a `reduction` in 'blocks' of free space, at the same time source
subvol gains certain 'blocks' of free space. A valid check is
- necessary here to avoid errorneous move to destination where
+ necessary here to avoid erroneous move to destination where
the space could be scantily available.
- With heterogenous brick support, an actual space comparison could
+ With heterogeneous brick support, an actual space comparison could
prevent any files being migrated to newly added bricks if they are
smaller then the free space available on the existing bricks.
*/
@@ -1119,7 +1119,7 @@ find_new_subvol:
if ((!(*new_subvol)) || (*new_subvol == from)) {
gf_msg (this->name, GF_LOG_WARNING, 0,
DHT_MSG_SUBVOL_INSUFF_SPACE, "Could not find any subvol"
- " with space accomodating the file - %s. Consider "
+ " with space accommodating the file - %s. Consider "
"adding bricks", loc->path);
*target_changed = _gf_false;
@@ -3363,7 +3363,7 @@ gf_defrag_get_entry (xlator_t *this, int i, struct dht_container **container,
tmp_container->df_entry->dict =
dict_ref (df_entry->dict);
- /*Build Container Structue >> END*/
+ /*Build Container Structure >> END*/
ret = 0;
goto out;
@@ -3670,7 +3670,7 @@ gf_defrag_settle_hash (xlator_t *this, gf_defrag_info_t *defrag,
if (conf->local_subvols_cnt == 0 || !conf->lookup_optimize) {
/* Commit hash updates are only done on local subvolumes and
- * only when lookup optmization is needed (for older client
+ * only when lookup optimization is needed (for older client
* support)
*/
return 0;