=== mgagne is now known as Guest73233 === cpaelzer is now known as cpaelzer_afk === cpaelzer_afk is now known as cpaelzer === cpaelzer is now known as cpaelzer_afk === cpaelzer_afk is now known as cpaelzer === cpaelzer is now known as cpaelzer_afk === cpaelzer_afk is now known as cpaelzer [18:52] hello, i am in desperate need of help; i am tired of uploading failed images [18:52] i am building a lvm+xfs centos7 machine, and cloud-init won't grow the root filesystem no matter what i try [18:53] i have make sure growpart is available and lvm + xfs tools [18:53] made* [19:15] growpart does not work on lvm devices. [19:16] natorious, thought he might add taht support, or might have another solution for you. [19:16] cornfeedhobo, ^ [19:20] that explains alot === cpaelzer is now known as cpaelzer_afk [19:39] you would think lvm support would be more demanded. it makes dealing with a few things much better [20:08] natorious: i would be interested in hearing what you would suggest [20:40] cornfeedhobo, i am becomming more interested in it. [20:40] but largely lvm is not that improtant in "cloud" . stricktly because yoru OS disk is just easilyi small and ptu other things on other disks. [20:44] well, for example, resizing [20:45] without lvm on aws, you must stop, detach. snapshot. relauch as larger. resize. [20:45] with, you just create a new volume, attach, add to lvm, resize [20:45] its a bit like a jbod then, but no downtime [20:46] ok. the response woudl be that you should not do that on your OS disk [20:46] that make sense ? i do see the value, and woudl accept patches to cloud-init or growpart. [20:47] but just keep your data on an ebs volume that you make an lvm on [20:47] and keep your os disk small and OS only. [20:49] hmmm [20:51] ya there is some logic to that, isn't there [20:57] smoser: i'll brb. i also had a plan ext4 image that wasn't expanding also, but i think i know what that problem was. should be back around in about an hour and a half