Description of problem:
========================
On a setup which has a volume, say 'ozone' with multiple block devices created in it, volume stop/delete succeeds. 
- No warnings mentioning that there are block devices present. 
- No failure, probing the user to take-care-of exported block devices in it. 
It. Just. Deletes. And along with it goes the existence of all the blocks.

Further,
'gluster-block list ozone' prints "Not able to create Metadata on volume ozone (Transport endpoint not connected)" - which ideally should have been "Volume ozone does not exist"

Both the things above give me the impression that the system has been left in an _unclean_ state.

Version-Release number of selected component (if applicable):
============================================================
glusterfs-3.8.4-31 and gluster-block-0.2.1-4


How reproducible:
================
I have just tried it once, but it is safe to assume it is going to happen every time..


Additional info:
===================

[root@dhcp47-115 ~]# gluster-block list ozone
testblock2
testblock3
testblock4
testblock5
testblock6
testblock7
block
testblock
[root@dhcp47-115 ~]#
[root@dhcp47-115 ~]# gluster v stop ozone
Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y
volume stop: ozone: success
[root@dhcp47-115 ~]# gluster v delete ozone
Deleting volume will erase all information about the volume. Do you want to continue? (y/n) y
volume delete: ozone: success
[root@dhcp47-115 ~]# 
[root@dhcp47-115 ~]# gluster-block list ozone
Not able to create Metadata on volume ozone[Transport endpoint is not connected]
[root@dhcp47-115 ~]# 
[root@dhcp47-115 ~]# gluster-block info ozone/testblock2
Not able to create Metadata on volume ozone[Transport endpoint is not connected]
[root@dhcp47-115 ~]#