growpart does not work for lvm
Bug #1799953 reported by
Scott Moser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Medium
|
Unassigned | ||
cloud-utils |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Similar to bug 1491148, growpart does not support growing a lvm device.
It would be good if growpart in conjunction with cloud-init could
recognize that the filesystem was on a volume and grow the underlying
partition or volume group.
Related bugs:
bug 1491148: growpart doesn't work with mdraid devices
Changed in cloud-init: | |
status: | New → Confirmed |
Changed in cloud-utils: | |
status: | New → Confirmed |
Changed in cloud-init: | |
status: | Confirmed → Triaged |
Changed in cloud-utils: | |
status: | Confirmed → Triaged |
Changed in cloud-init: | |
importance: | Undecided → Medium |
Changed in cloud-utils: | |
importance: | Undecided → Medium |
Changed in cloud-utils: | |
status: | Triaged → In Progress |
To post a comment you must log in.
If this is accurate, I suspect the bug is in the cloud-init call to growpart, as I am using 0.31 successfully on CentOS 7 appliances with a LVM. There obviously are further steps needed to extend the LVM PV and LVs, along with the filesystem, but 0.31 seems to work well at growing the raw disk partition (we had to use the project release of 0.31 because the EL7 bundled package includes a much older release that mangles 2TB > GPT disks due to Bug #1259703).