<br><br><div class="gmail_quote">On Wed, Oct 27, 2010 at 6:19 PM, Justin Riley <span dir="ltr"><<a href="mailto:jtriley@mit.edu">jtriley@mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"> On 10/27/10 4:22 PM, Dan Tenenbaum wrote:<br>
> I formatted the volume according to your instructions below and<br>
> everything worked.<br>
><br>
> BTW, everything done with ElasticFox in those instructions can now be<br>
> done in the AWS console (which is how I did it). For those who don't<br>
> use firefox. ;)<br>
><br>
> Dan<br>
</div>Glad you found a solution for now. There certainly seems to be something<br>
up with the createvolume command. You are using 0.91 (or the recent<br>
identical 0.91.1) release correct? I'll install it in a separate vm and<br>
test it out to see if I can reproduce the issues.<br></blockquote><div><br></div><div>Hi Justin,</div><div><br></div><div>To answer your earlier question, I just ran startconsole with the same zone every time.</div><div>
All of our EBS volumes are in us-east-1d, so I don't want to do anything in any other zone.</div><div><br></div><div>I did run the command more than once, but after each invocation, I killed the cluster that was created.</div>
<div><br></div><div>I didn't pay close enough attention, but I think sometimes perhaps the stop cluster command displays instance IDs of instances that have already stopped.</div><div><br></div><div>Or, is it looking in my config file and starting up the number of nodes I have defined there?</div>
<div><br></div><div>Anyway, thanks for looking into it.</div><div><br></div><div>I am running 0.91.</div><div><br></div><div>Thanks</div><div>Dan</div><div><br></div></div>