AWS EBS Volume "in-use - optimizing"

Question

I have an EBS volume that displays a state of "in-use - optimizing(%)". What does this mean? What are the optimizations that AWS is performing? This is on a 300gb encrypted gp2 volume attached to a Windows Server 2012 R2 EC2 instance.

Commit

Answer 1

The in-use - optimizing state relates to EBS volume resizing.

• in-use indicates that this volume is attached to an EC2 instance.
• optimizing is the volume's modification state.

According to the AWS documentation on volume modifications:

An EBS volume being modified goes through a sequence of states. After you issue a ModifyVolume directive, whether from the console, CLI, API, or SDK, the volume enters first the Modifying state, then the Optimizing state, and finally the Complete state.

...

While the volume is in the optimizing state, your volume performance is in between the source and target configuration specifications. Transitional volume performance will be no less than the source volume performance. If you are downgrading IOPS, transitional volume performance is no less than the target volume performance.

And finally, from the introductory blog post for Volume Modifications:

The volume’s state reflects the progress of the operation (modifying, optimizing, or complete):

Woe

it's showing in-use - optimizing (64%) for me I modified from 50Gb to 80GG , now want to make it 100Gb but not able to due to in-use - optimizing (64%) so how much time will it require to be 100% , after that will I be able to modify to 100Gb or not ? – Cabriole

I personally noticed that the volume was available for "extending" in windows before the EBS volume was done optimizing. AWS also states you can do it while still optimizing: docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/… – Gord

Will detaching the volume speed things up? Anything I can do to hurry this along? – Windflower

For linux folks here, you can resize the filesystem to the full size while it's optimizing. However you need to run sudo e2fsck -f /dev/yourdevice before sudo resize2fs /dev/yourdevice. e2fsck doesn't take very long (about 1 minute for 70GB) – Stutsman

@SamuelPrevost can you elaborate on why e2fsck is necessary? Is it only necessary if you are resizing offline? Because just running sudo resize2fs /dev/[device] has always worked for me for online resizing when /dev/[device] is mounted unix.stackexchange.com/questions/446934/… – Lagunas

@NickMeyer e2fsck checks the integrity of the ext4 filesystem. It sounded like a good thing to do before manipulating the size of the file system. resize2fs's doc says that as of Linux 2.6, the kernel support online resizing for ext3 and ext4. When offline, it's not necessary because there's no operations in cache anyway. I just don't want to chance it so I run the fsck just in case. – Stutsman

Late to the party, but I asked the same question and ended up here. However, I'm not sure any of this actually answers the question 'What are the optimizations that AWS is performing?' - can anyone explain what is actually happening to to disk whilst the 'optimization' is going on? – Hardnett

Answer 2

If you modified the volume, most likely it will show like that. The performance will be degraded during this time since AWS EBS server needs to sync data.

Hildegardehildesheim

IN Free trial, for my AWS EC2 instance modified and I could see volume as "in-use - completed (100%)" but still C-Drive space is 30G only. why? – Zoellick

@Zoellick after you change volume size and wait to complete the optimizing you need to EXTEND your partition and filesystem, docs here docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/… – Uriah

Try to perform the expansion when the disk I/O load is low. – Oral

Answer 3

EBS Volumes are in this state after modifying the volume (e.g. resizing). It can take some time (can be stuck at 99% for hours) but eventually will go away.

Nonferrous