[StarCluster] starcluster resizevolume fails

Ryan Golhar ngsbioinformatics at gmail.com
Thu Nov 1 21:47:27 EDT 2012


I have a 20GB EBS that I'm trying to resize to 200GB.  I used resizevolume
but got an error:

[ec2-user at awsmicro ~]$ starcluster resizevolume vol-6109f51c 200
StarCluster - (http://web.mit.edu/starcluster) (v. 0.93.3)
Software Tools for Academics and Researchers (STAR)
Please submit bug reports to starcluster at mit.edu

>>> No keypair specified, picking one from config...
>>> Using keypair: aws_starcluster_keypair
>>> Creating security group @sc-volumecreator...
>>> No instance in group @sc-volumecreator for zone us-east-1a, launching
one now.
Reservation:r-d32d39b5
>>> 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.200 mins
>>> Checking for required remote commands...
>>> Creating snapshot of volume: vol-6109f51c
>>> Waiting for snapshot to complete: snap-cac8e1bc
snap-cac8e1bc: |||||||||||||||||||||||||||||||||||||||||||||100% Time:
00:30:15
>>> Creating 200GB volume in zone us-east-1a from snapshot snap-cac8e1bc
>>> New volume id: vol-b46254c9
>>> Waiting for new volume to become 'available'...
>>> Attaching volume vol-b46254c9 to instance i-23afed5f...
>>> No partitions found, resizing entire device
!!! ERROR - command 'resize2fs /dev/xvdz' failed with status 1
>>> Removing generated snapshot snap-cac8e1bc
>>> Leaving volume vol-b46254c9 attached to instance i-23afed5f
>>> Not terminating host instance i-23afed5f
*** WARNING - There are still volume hosts running: i-23afed5f
*** WARNING - Run 'starcluster terminate volumecreator' to terminate *all*
volume host instances once they're no longer needed
>>> Volume vol-6109f51c was successfully resized to 200GB
>>> New volume id is: vol-b46254c9


It turns out, e2fsck needs to be run first:

root at ip-10-158-10-170:~# resize2fs /dev/xvdz
resize2fs 1.41.14 (22-Dec-2010)
Please run 'e2fsck -f /dev/xvdz' first.

root at ip-10-158-10-170:~# e2fsck -f /dev/xvdz
e2fsck 1.41.14 (22-Dec-2010)
/dev/xvdz: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/xvdz: ***** FILE SYSTEM WAS MODIFIED *****
/dev/xvdz: 9852/1310720 files (0.3% non-contiguous), 3152127/5242880 blocks
root at ip-10-158-10-170:~# resize2fs /dev/xvdz
resize2fs 1.41.14 (22-Dec-2010)
Resizing the filesystem on /dev/xvdz to 52428800 (4k) blocks.
The filesystem on /dev/xvdz is now 52428800 blocks long.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/starcluster/attachments/20121101/12027137/attachment.htm


More information about the StarCluster mailing list