View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017659 | CentOS-8 | -OTHER | public | 2020-08-10 07:01 | 2020-08-18 04:51 |
| Reporter | tiendungitd | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 8.2.2004 | ||||
| Summary | 0017659: AWS EC2 could not expand EBS volume when using Centos 8 AMI Offical | ||||
| Description | I'm using Offical Centos public images in https://wiki.centos.org/Cloud/AWS to launch EC2 instance, more detail I'm using T3.micro instant type. After I modified volume size in AWS console, I can see a new size has been show in lsblk output command: [root@ip-10-135-3-109 centos]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 12G 0 disk ├─nvme0n1p1 259:1 0 1M 0 part └─nvme0n1p2 259:2 0 10G 0 part / [root@ip-10-135-3-109 centos]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 367M 0 367M 0% /dev tmpfs 396M 0 396M 0% /dev/shm tmpfs 396M 11M 386M 3% /run tmpfs 396M 0 396M 0% /sys/fs/cgroup /dev/nvme0n1p2 10G 2.4G 7.7G 24% / tmpfs 80M 0 80M 0% /run/user/1000 However, I could not extend the partition on the root volume [root@ip-10-135-3-109 centos]# growpart /dev/nvme0n1 1 NOCHANGE: partition 1 is size 2048. it cannot be grown If I reboot EC2, the instance can automatically extend the partition, but I don't want any downtime when expand EBS like this way. Any idea or what might causing this issue? | ||||
| Tags | AMI, aws, ebs | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-08-10 07:01 | tiendungitd | New Issue | |
| 2020-08-10 07:01 | tiendungitd | Tag Attached: AMI | |
| 2020-08-10 07:01 | tiendungitd | Tag Attached: aws | |
| 2020-08-10 07:01 | tiendungitd | Tag Attached: ebs | |
| 2020-08-18 04:51 | tiendungitd | Note Added: 0037569 |
