<div class="gmail_quote">2012/5/2 Arnold Krille <span dir="ltr"><<a href="mailto:arnold@arnoldarts.de" target="_blank">arnold@arnoldarts.de</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As far as I understand it (and for the current stable 3.2) there are two ways<br>
depending on what you want:<br>
When you want a third copy of the data, it seems you can't simply increase<br>
the replication-level and add a brick. Instead you have to stop usage, delete<br>
the volume (without deleting the underlying bricks of course) and then rebuild<br>
the volume with the new number of replication and bricks. Then self-heal<br>
should do the trick and copy the data onto the third machine.<br></blockquote><div><br></div><div>I can't stop a production volume used by many customers.</div><div>I think that the best way should start with the correct number of replication nodes</div>
<div>even if one of these node is not present.</div><div><br></div><div>In this way, the volume is created properly, and when needed I have to just add</div><div>the new machine and trigger the self-healing.</div><div><br>
</div></div>