HI, using gluster in replicated, we have the following conf:<br><br>Volume Name: volume01<br>Type: Distributed-Replicate<br>Status: Started<br>Number of Bricks: 4 x 2 = 8<br>Transport-type: tcp<br>Bricks:<br>Brick1: gluster01:/mnt<br>
Brick2: gluster02:/mnt<br>Brick3: gluster03:/mnt<br>Brick4: gluster04:/mnt<br>Brick5: gluster05:/mnt<br>Brick6: gluster06:/mnt<br>Brick7: gluster51:/mnt<br>Brick8: gluster52:/mnt<br>Options Reconfigured:<br>cluster.data-self-heal-algorithm: full<br>
performance.io-thread-count: 64<br>diagnostics.brick-log-level: INFO<br><br><br>The we did:<br><br>gluster volume stop volume01<br><br>And it took several minutes, after that running gluster volume info gives:<br><br><br>
Volume Name: volume01<br>Type: Distributed-Replicate<br>Status: Stopped<br>Number of Bricks: 4 x 2 = 8<br>Transport-type: tcp<br>Bricks:<br>Brick1: gluster01:/mnt<br>Brick2: gluster02:/mnt<br>Brick3: gluster03:/mnt<br>Brick4: gluster04:/mnt<br>
Brick5: gluster05:/mnt<br>Brick6: gluster06:/mnt<br>Brick7: gluster51:/mnt<br>Brick8: gluster52:/mnt<br>Options Reconfigured:<br>cluster.data-self-heal-algorithm: full<br>performance.io-thread-count: 64<br>diagnostics.brick-log-level: INFO<br>
<br><br>But now if I do: gluster volume start volume01, gives the following error:<br><br>operation failed<br><br>If I do gluster volume reset the same thing:<br><br>gluster volume reset volume01<br>operation failed<br><br>
And if I try to stop again:<br><br>gluster volume stop volume01<br>Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y<br>operation failed<br><br><br>This occurs using gluster 3.2 on Centos 6.0<br>
<br><br>Where do I start looking so I can start the volume again?<br><br>Thanks<br>MV<br>