I have a 20GB EBS that I'm trying to resize to 200GB. I used resizevolume but got an error:<div><br></div><div><div>[ec2-user@awsmicro ~]$ starcluster resizevolume vol-6109f51c 200</div><div>StarCluster - (<a href="http://web.mit.edu/starcluster">http://web.mit.edu/starcluster</a>) (v. 0.93.3)</div>
<div>Software Tools for Academics and Researchers (STAR)</div><div>Please submit bug reports to <a href="mailto:starcluster@mit.edu">starcluster@mit.edu</a></div><div><br></div><div>>>> No keypair specified, picking one from config...</div>
<div>>>> Using keypair: aws_starcluster_keypair</div><div>>>> Creating security group @sc-volumecreator...</div><div>>>> No instance in group @sc-volumecreator for zone us-east-1a, launching one now.</div>
<div>Reservation:r-d32d39b5</div><div>>>> Waiting for volume host to come up... (updating every 30s)</div><div>>>> Waiting for all nodes to be in a 'running' state...</div><div>1/1 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| 100%</div>
<div>>>> Waiting for SSH to come up on all nodes...</div><div>1/1 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| 100%</div><div>>>> Waiting for cluster to come up took 1.200 mins</div>
<div>>>> Checking for required remote commands...</div><div>>>> Creating snapshot of volume: vol-6109f51c</div><div>>>> Waiting for snapshot to complete: snap-cac8e1bc</div><div>snap-cac8e1bc: |||||||||||||||||||||||||||||||||||||||||||||100% Time: 00:30:15</div>
<div>>>> Creating 200GB volume in zone us-east-1a from snapshot snap-cac8e1bc</div><div>>>> New volume id: vol-b46254c9</div><div>>>> Waiting for new volume to become 'available'...</div>
<div>>>> Attaching volume vol-b46254c9 to instance i-23afed5f...</div><div>>>> No partitions found, resizing entire device</div><div>!!! ERROR - command 'resize2fs /dev/xvdz' failed with status 1</div>
<div>>>> Removing generated snapshot snap-cac8e1bc</div><div>>>> Leaving volume vol-b46254c9 attached to instance i-23afed5f</div><div>>>> Not terminating host instance i-23afed5f</div><div>*** WARNING - There are still volume hosts running: i-23afed5f</div>
<div>*** WARNING - Run 'starcluster terminate volumecreator' to terminate *all* volume host instances once they're no longer needed</div><div>>>> Volume vol-6109f51c was successfully resized to 200GB</div>
<div>>>> New volume id is: vol-b46254c9</div></div><div><br></div><div><br></div><div>It turns out, e2fsck needs to be run first:</div><div><br></div><div><div>root@ip-10-158-10-170:~# resize2fs /dev/xvdz</div><div>
resize2fs 1.41.14 (22-Dec-2010)</div><div>Please run 'e2fsck -f /dev/xvdz' first.</div><div><br></div><div>root@ip-10-158-10-170:~# e2fsck -f /dev/xvdz</div><div>e2fsck 1.41.14 (22-Dec-2010)</div><div>/dev/xvdz: recovering journal</div>
<div>Pass 1: Checking inodes, blocks, and sizes</div><div>Pass 2: Checking directory structure</div><div>Pass 3: Checking directory connectivity</div><div>Pass 4: Checking reference counts</div><div>Pass 5: Checking group summary information</div>
<div><br></div><div>/dev/xvdz: ***** FILE SYSTEM WAS MODIFIED *****</div><div>/dev/xvdz: 9852/1310720 files (0.3% non-contiguous), 3152127/5242880 blocks</div><div>root@ip-10-158-10-170:~# resize2fs /dev/xvdz</div><div>resize2fs 1.41.14 (22-Dec-2010)</div>
<div>Resizing the filesystem on /dev/xvdz to 52428800 (4k) blocks.</div><div>The filesystem on /dev/xvdz is now 52428800 blocks long.</div></div><div><br></div><div><br></div>