[Bugs] [Bug 1278390] Data Tiering:Regression:Detach tier commit is passing when detach tier is in progress
bugzilla at redhat.com
bugzilla at redhat.com
Tue Nov 17 12:30:43 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1278390
Bhaskarakiran <byarlaga at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |ASSIGNED
CC| |byarlaga at redhat.com
--- Comment #3 from Bhaskarakiran <byarlaga at redhat.com> ---
Check this on 3.7.5-6 build. If detach-tier is done from the node where the
scan is complete, commit is successful though other node is in progress. If
detach-tier is done from the node where scan is in progress, correct error
message is shown and detach-tier fails. Moving back the bug.
[root at transformers yum.repos.d]# gluster v detach-tier vol1 status
Node Rebalanced-files size
scanned failures skipped status run time in secs
--------- ----------- -----------
----------- ----------- ----------- ------------ --------------
localhost 0 0Bytes
116983 0 0 completed 600.00
ninja 0 0Bytes
0 0 0 in progress 0.00
[root at transformers yum.repos.d]# gluster v detach-tier vol1 commit
Removing tier can result in data loss. Do you want to Continue? (y/n) y
volume detach-tier commit: success
Check the detached bricks to ensure all files are migrated.
If files with data are found on the brick path, copy them via a gluster mount
point before re-purposing the removed brick.
[root at transformers yum.repos.d]#
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=7uDRKFSdGk&a=cc_unsubscribe
More information about the Bugs
mailing list