+++ This bug was initially created as a clone of Bug #1142087 +++

Description of problem:
-----------------------
'remove-brick force' was used to forcefully remove the brick from the volume, knowing that there would be data lost in that case. There is no data migration involved with 'remove-brick force'

But as of now, with the latest build, there is a warning thrown, suggesting the user to copy the data from the removed brick to the gluster mount, if the files are not migrated.

This arises contradiction.

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
glusterfs-3.6.0.28-1.el6rhs

How reproducible:
------------------
Always

Steps to Reproduce:
-------------------
1. Create a distributed volume
2. Try removing a brick forcefully

Actual results:
---------------
Warning message is thrown to copy back the data from the removed-brick to gluster mount ( if there are any data available on removed brick )

[root@rhss5 ~]# gluster volume remove-brick repvol NODE1:/rhs/brick1/b1 NODE2:/rhs/brick1/b1 force
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: success
Check the removed 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. 

Expected results:
-----------------
The warning message should not be thrown, as there is no data migration is involved with 'remove-brick force'

Additional Info
----------------
The intent of 'remove-brick  force' is to remove the brick forcefully ignoring the data in it. We confirm the same before executing 'remove-brick force' saying - "Removing brick(s) can result in data loss. Do you want to Continue? (y/n)"

Again after executing 'remove-brick force' again warning message is thrown as - 
"Check the removed 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.", which would be contradicting.

--- Additional comment from SATHEESARAN on 2014-09-16 12:15:19 MVT ---

Example :

[root@rhss5 ~]# gluster volume remove-brick repvol NODE1:/rhs/brick1/b1 NODE2:/rhs/brick1/b1 force
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: success
Check the removed 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.

--- Additional comment from Nagaprasad Sathyanarayana on 2014-09-17 10:23:32 MVT ---

As discussed and agreed by engineering leads, this is to be targeted for the 3.0.2 release.

--- Additional comment from Shalaka on 2014-09-18 10:52:37 MVT ---

Please add doc text for this known issue.

--- Additional comment from Nithya Balachandran on 2014-09-22 10:22:34 MVT ---

I would say we can probably skip documenting this as known issue as the only thing we can say is that the user can ignore the message in this scenario.

--- Additional comment from Shalaka on 2014-09-26 10:54:14 MVT ---

Canceling need_info as Nithya reviewed and signed-off the doc text.