<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><BR>
<BR>
<div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Joe can offer more information but I would delete the existing volume…which will leave the data….<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Then recreate the volume as a distribute-replica by doing…<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Gluster volume create gluster-ssd-vol replica 2 transport tcp 1A 1B 2A 2B 3A 3B 4A 4B 5A 5B 6A 6B 7A 7B 8A 8B<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The order in which you add the brick determines the replica sets…<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>This will use the brick from the previous volume and mirror it with a new brick….then run a self heal and they will sync…<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Bryan<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> gluster-users-bounces@gluster.org [mailto:gluster-users-bounces@gluster.org] <b>On Behalf Of </b>Kushnir, Michael (NIH/NLM/LHC) [C]<br><b>Sent:</b> Tuesday, November 06, 2012 11:45 AM<br><b>To:</b> 'gluster-users@gluster.org'<br><b>Subject:</b> Re: [Gluster-users] Instructions for converting a distributed volume to a distributed-replicated?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Thanks for getting back to me guys. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I don’t have an existing volume yet. This is a planned deployment. At first I will have one server with 8 bricks forming a distributed volume. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>So, on server 1, I will have volume “gluster-ssd-vol” with bricks: 1A, 2A, 3A, 4A, 5A, 6A, 7A, 8A.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Then (a week later) I will add server two and would like to convert to a distributed-replicated volume by adding bricks: 1B, 2B, 3B, 4B, 5B, 6B, 7B, 8B. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>So would “gluster volume add-brick gluster-ssd-vol replica 2 <1B> <2B> <3B> <4B> <5B> <6B> <7B> <8B>” result in a distributed-replicated volume with replica sets 1AB, 2AB, 3AB, etc…?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Michael<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Joe Julian [<a href="mailto:joe@julianfamily.org">mailto:joe@julianfamily.org</a>] <br><b>Sent:</b> Tuesday, November 06, 2012 12:23 PM<br><b>To:</b> 'gluster-users@gluster.org'<br><b>Subject:</b> Re: [Gluster-users] Instructions for converting a distributed volume to a distributed-replicated?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The text isn't 100% clear, I agree, but it is safe to infer from this what you would naturally infer:<o:p></o:p></p><pre># gluster volume add-brick<o:p></o:p></pre><pre>Usage: volume add-brick <VOLNAME> [<stripe|replica> <COUNT>] <NEW-BRICK> ...<o:p></o:p></pre><p class=MsoNormal style='margin-bottom:12.0pt'>meaning you can add-brick, specify the new replica (or stripe) count and list enough bricks to make the change possible and it will do just that.<o:p></o:p></p><div><p class=MsoNormal>On 11/05/2012 10:30 AM, Kushnir, Michael (NIH/NLM/LHC) [C] wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>Hi everyone,<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Where can I find instructions for converting a distributed volume to a distributed replicated volume? <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Michael<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>______________________________________________________________________________________<o:p></o:p></p><p class=MsoNormal>Michael Kushnir<o:p></o:p></p><p class=MsoNormal>System Architect / Engineer <o:p></o:p></p><p class=MsoNormal>Communications Engineering Branch<o:p></o:p></p><p class=MsoNormal>Lister Hill National Center for Biomedical Communications<o:p></o:p></p><p class=MsoNormal>National Library of Medicine<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>8600 Rockville Pike, Building 38A, Floor 10<o:p></o:p></p><p class=MsoNormal>Besthesda, MD 20894<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Phone: 301-435-3219<o:p></o:p></p><p class=MsoNormal>Email: <a href="mailto:michael.kushnir@nih.gov">michael.kushnir@nih.gov</a> <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><img border=0 width=155 height=102 id="Picture_x0020_1" src="cid:image001.jpg@01CDBC17.485E9440" alt=VMW-LGO-CERTIFIED-PRO-5-K><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br><br><o:p></o:p></span></p><pre>_______________________________________________<o:p></o:p></pre><pre>Gluster-users mailing list<o:p></o:p></pre><pre><a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><o:p></o:p></pre><pre><a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><o:p></o:p></pre></blockquote><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p></div>
<br>
<br>
<font size="1">
NOTICE: This email and any attachments may contain confidential and proprietary information of NetSuite Inc. and is for the sole use of the intended recipient for the stated purpose. Any improper use or distribution is prohibited. If you are not the intended recipient, please notify the sender; do not review, copy or distribute; and promptly delete or destroy all transmitted information. Please note that all communications and information transmitted through this email system may be monitored by NetSuite or its agents and that all incoming email is automatically scanned by a third party spam and filtering service.
</font>
</body></html>