[Gluster-users] Clarification on common tasks

[Gandalf Corvotempesta]

2016-08-11 16:34 GMT+02:00 Joe Julian <joe at julianfamily.org>:
> When you replace a brick, the new filesystem will not have that attribute so "force" is required to override that safety check.

IMHO,  as we are not *starting* the volume (is already started)
another command should be used.
If you do a "gluster v status" even with a failed brick, the command
runs properly and output the volume status, because is already
started.
I think that another command would be better to create less confusion
to who is new to gluster.

my 2 cents.