How to reconfigure a faulty brick with another brick of same UUID in a distributed-dispersed volume

Issue

• Need to replace a faulty brick with same UUID due to LV corruption in initial brick. The initial brick is offline in the volume.

# gluster volume status dev_backup

[output removed for online bricks]
Brick servera:/gluster/brick1/1       N/A      N/A      N      N/A

• If the other bricks of the sub-volume is online in the gluster cluster, we can do a brick reset to reset the faulty brick. 'reset-brick' lets you replace a brick with another brick of the same location and UUID.