diff options
author | Amar Tumballi <amar@gluster.com> | 2010-08-09 05:43:01 +0000 |
---|---|---|
committer | Anand V. Avati <avati@dev.gluster.com> | 2010-08-11 22:24:38 -0700 |
commit | b8779318dd2d99e44f54de741beee32f55553e75 (patch) | |
tree | 58d4d0dace2484b60c4b870c761d1182b529bfe7 /xlators/performance | |
parent | 0b501ac95edc0ef5945228eb47e6482cfc4efa41 (diff) |
fuse resolve related changes
Now fuse is fully complaint with DVM, as even if there is a fop
request on inode belonging to old graph, it will be resolved
corresponding to new graph and operations will be performed wrt.
new graph, which makes DVM truely spontaneous.
Signed-off-by: Amar Tumballi <amar@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
BUG: 1240 (DVM: after graph change, inodes should resolve to new inode-table)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1240
Diffstat (limited to 'xlators/performance')
-rw-r--r-- | xlators/performance/write-behind/src/write-behind.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/xlators/performance/write-behind/src/write-behind.c b/xlators/performance/write-behind/src/write-behind.c index d9fe41907..23f2d56b9 100644 --- a/xlators/performance/write-behind/src/write-behind.c +++ b/xlators/performance/write-behind/src/write-behind.c @@ -436,7 +436,7 @@ wb_sync (call_frame_t *frame, wb_file_t *file, list_head_t *winds) } if (total_count == 0) { - gf_log (file->this->name, GF_LOG_DEBUG, "no vectors are to be" + gf_log (file->this->name, GF_LOG_TRACE, "no vectors are to be" "synced"); goto out; } |