Description of problem:
-----------------------
Creating a gluster volume level snapshot, while one of the node in the 'Trusted Storage Pool' ( gluster cluster ) is down, does provides the warning that one of the node is down and suggests to use 'force' option to override this behaviour.

But when using 'force' option in creating snapshot again throws the errors out saying that quorum is not met.

Thus the suggestion to create snapshot with force option becomes a wrong suggestion


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
glusterfs-3.7.1-5.el6rhs

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

Steps to Reproduce:
--------------------
1. Create a 'Trusted Storage Pool'
2. Create a distributed volume and start it
3. Stop glusterd in one of the node
4. Create snapshot
5. Create snapshot with force option 

Actual results:
---------------
Snapshot create failed and volume snapshot suggested to use 'force' option to override this behaviour.
Using 'force' option again failed saying that quorum is not met

Expected results:
----------------
1. If the snapshot create is not allowed, when one of the node is down, then it should be explicitly informed.
2. Suggestion to use 'force' with snapshot create should be removed

Additional info:
----------------
Below is the console log, where snapshot creation is attempted, when one of the node in the cluster is down.

[root@~]# gluster snapshot create snap1 r3v
snapshot create: failed: One or more bricks are not running. Please run volume status command to see brick status.
Please start the stopped brick and then issue snapshot create command or use [force] option in snapshot create to override this behavior.
Snapshot command failed

[root@ ~]# gluster snapshot create snap1 r3v force
snapshot create: failed: One or more bricks may be down.
Snapshot command failed