-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Paolo,
My apologies for the delay, just got back from vacation. You're
correct there is a bug in the createvolume command in the latest
version of StarCluster. In the latest Ubuntu AMIs the volume devices
now show up as /dev/xvd* instead of /dev/sd*.
I'll try to put out another patch release (0.93.2) by tomorrow. For
the time being you can get around this by specifying one of the older
AMIs (see listpublic command). For example, in us-east-1:
$ starcluster createvolume -i ami-d1c42db8 10 us-east-1c
This will launch the host instance using the old Ubuntu 9.10
StarCluster AMI which should work. I'll post an announcement to the
list when 0.93.2 is ready.
Hope that helps,
~Justin
On 01/30/2012 10:36 AM, Paolo Di Tommaso wrote:
> Dear StarCluster,
>
> Sorry if I'm bothering still with this problem, but it seems that
> there is a bug with the createvolume command in the latest
> starcluster version.
>
> Trying to create a new volume with starcluster I get the error
> below. The same command with an older version works without any
> problem.
>
> Could you please confirm that this is an issue ?
>
>
> Cheers, Paolo
>
>
>
> *$ starcluster createvolume -n "lab-tools" 1 us-east-1d*
> StarCluster - (http://web.mit.edu/starcluster) (v. 0.93.1)
> Software Tools for Academics and Researchers (STAR) Please submit
> bug reports to starcluster_at_mit.edu <mailto:starcluster_at_mit.edu>
>
>>>> No keypair specified, picking one from config... Using
>>>> keypair: maquito Creating security group _at_sc-volumecreator...
>>>> No instance in group _at_sc-volumecreator for zone us-east-1d,
>>>> launching
> one now. Reservation:r-9c1ae9fc
>>>> Waiting for volume host to come up... (updating every 30s)
>>>> Waiting for all nodes to be in a 'running' state...
> 1/1
> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>
>
>
100%
>>>> Waiting for SSH to come up on all nodes...
> 1/1
> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>
>
>
100%
>>>> Waiting for cluster to come up took 1.313 mins Checking for
>>>> required remote commands... Creating 1GB volume in zone
>>>> us-east-1d New volume id: vol-c4fb1da8 Waiting for new
>>>> volume to become 'available'... Attaching volume vol-c4fb1da8
>>>> to instance i-cb598bae... Formatting volume...
> *mke2fs 1.41.14 (22-Dec-2010)* * * *mkfs.ext3: No such file or
> directory while trying to determine filesystem size* * * *!!!
> ERROR - command 'mkfs.ext3 -F /dev/sdz' failed with status 1*
>>>> Leaving volume vol-c4fb1da8 attached to instance i-cb598bae
>>>> Not terminating host instance i-cb598bae
> *** WARNING - There are still volume hosts running: i-cb598bae ***
> WARNING - Run 'starcluster terminate volumecreator' to terminate
> *all* volume host instances once they're no longer needed
>>>> Your new 1GB volume vol-c4fb1da8 has been created
>>>> successfully Creating volume took 1.742 mins
>
>
>
> On Jan 24, 2012, at 6:10 PM, Paolo Di Tommaso wrote:
>
>> Dear all,
>>
>> When I try to create an new volume using the createvolume
>> command I get the following error:
>>
>>>>> Formatting volume...
>> mke2fs 1.41.14 (22-Dec-2010) mkfs.ext3: No such file or
>> directory while trying to determine filesystem size !!! ERROR -
>> command 'mkfs.ext3 -F /dev/sdz' failed with status 1
>>
>>
>> Despite that the command itself does not terminate with an error
>> (below the complete trace).
>>
>> But when I try to start a cluster instance using that volume, it
>> will not be attached.
>>
>>
>> Is this a bug or I'm missing something ?
>>
>>
>> Thank you, Paolo
>>
>>
>>
>>
>>
>>
>> *$ starcluster createvolume --tag=lab-soft 10 us-east-1d
>> StarCluster - (http://web.mit.edu/starcluster) (v. 0.93.1)
>> Software Tools for Academics and Researchers (STAR) Please
>> submit bug reports to starcluster_at_mit.edu
>> <mailto:starcluster_at_mit.edu>
>>
>>>>> No keypair specified, picking one from config... Using
>>>>> keypair: maquito Creating security group
>>>>> _at_sc-volumecreator... No instance in group
>>>>> _at_sc-volumecreator for zone us-east-1d,
>> launching one now. Reservation:r-537e6232
>>>>> Waiting for volume host to come up... (updating every 30s)
>>>>> Waiting for all nodes to be in a 'running' state...
>> 1/1
>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>
>>
>>
100%
>>>>> Waiting for SSH to come up on all nodes...
>> 1/1
>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>
>>
>>
100%
>>>>> Waiting for cluster to come up took 1.277 mins Checking
>>>>> for required remote commands... Creating 10GB volume in
>>>>> zone us-east-1d New volume id: vol-afa9a2c2 Waiting for
>>>>> new volume to become 'available'... Adding volume tag:
>>>>> lab-soft Attaching volume vol-afa9a2c2 to instance
>>>>> i-1faa407a... Formatting volume...
>> mke2fs 1.41.14 (22-Dec-2010)
>>
>> mkfs.ext3: No such file or directory while trying to determine
>> filesystem size
>>
>> !!! ERROR - command 'mkfs.ext3 -F /dev/sdz' failed with status 1
>>>>> Leaving volume vol-afa9a2c2 attached to instance i-1faa407a
>>>>> Not terminating host instance i-1faa407a
>> *** WARNING - There are still volume hosts running: i-1faa407a
>> *** WARNING - Run 'starcluster terminate volumecreator' to
>> terminate *all* volume host instances once they're no longer
>> needed
>>>>> Your new 10GB volume vol-afa9a2c2 has been created
>>>>> successfully Creating volume took 1.777 mins*
>>
>>
>>
>>
>>
>>
>> _______________________________________________ StarCluster
>> mailing list StarCluster_at_mit.edu <mailto:StarCluster_at_mit.edu>
>> http://mailman.mit.edu/mailman/listinfo/starcluster
>
>
>
> This body part will be downloaded on demand.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iEYEARECAAYFAk8mw3gACgkQ4llAkMfDcrlr0gCgh4saxvJNJz9OK/BcoSGzns2P
3UUAn3YsGTqwZ5b4vCrBVsZVtzzJHPJW
=dmoS
-----END PGP SIGNATURE-----
Received on Mon Jan 30 2012 - 11:21:17 EST