What should a SysOps administrator do to resolve this issue?
Extend the file system with operating system-level tools to use the new storage capacity.
Reattach the EBS volume to the EC2 instance.
Reboot the EC2 instance that is attached to the EBS volume.
Take a snapshot of the EBS volume. Replace the original volume with a volume that is created from the snapshot.
Explanations:
After increasing the size of the EBS volume, the operating system file system needs to be extended to recognize and utilize the additional space. On a Windows EC2 instance, this can be done using tools like Disk Management or thediskpartutility.
Reattaching the EBS volume to the EC2 instance does not solve the issue of file system size not being updated. The file system extension must be done at the OS level.
Rebooting the EC2 instance does not resolve the issue of the file system not recognizing the new volume size. The volume’s size change must be reflected at the OS level, which requires extending the file system.
Taking a snapshot and creating a new volume from it is unnecessary and does not address the underlying issue of the file system needing to be extended to use the new storage capacity.
I map out that the answer is:
Extend the file system with operating system-level tools to use the new storage capacity.