Glusterd daemon fails to start up after extending the underlying brick lvm.

Issue

• After extending an underlying brick and the filesystem, glusterd fails to start with the following message:

# gluster volume create vol1 machine1:/volumes/brick1
volume create: vol1: failed: Brick: machine1:/volumes/brick1 not available. Brick may be containing or be contained by an existing brick

• The underlying bricks were part of a logical volume. Increased the logical volume after adding/increasing underlying stroage.