=== vrubiolo1 is now known as vrubiolo [11:40] smoser, hey, don't see anything regarding LVM on cloud-utils-growpart, would have plans to do it? I have a couple of issues with customers using RHEL requesting it. [13:09] We just landed a fix for an issue that affects groovy (thanks rharper!), so I'm going to upload a new cloud-init to groovy. [13:16] what's groovy? [13:28] Odd_Bloke: nice! [13:28] meena: new ubuntu development release name Groovy Gorilla [13:29] 20.10? [13:29] yes [13:32] rharper: If you have a minute to validate: https://github.com/canonical/cloud-init/pull/486 [13:43] https://bugs.launchpad.net/cloud-init/+bug/1799953 [13:43] Ubuntu bug 1799953 in cloud-utils "growpart does not work for lvm" [Medium,Triaged] [13:43] otubo: ^ . I have no plans. but ^ is the bug that was created for the issue. [13:48] works for zfs [13:48] but then again, zfs is lvm + $fs in one [13:49] smoser, thanks [13:49] Odd_Bloke, do you guys plans to migrate issues from launchpad to github as well in the future? [13:51] otubo: Nope, we have to use Launchpad for Ubuntu issues/process regardless, so migrating "upstream" issues to GitHub would just leave us handling issues across two platforms. [14:25] otubo: https://bugs.launchpad.net/cloud-init/+bug/1799953 [14:25] Ubuntu bug 1799953 in cloud-utils "growpart does not work for lvm" [Medium,Triaged] [14:26] comment added there. it seems pretty easy. if you wanted to try [14:43] smoser: the only issue i see is using the device uuid, or some other link to it, instead of the device path [15:10] meena: ? [15:10] how so. [15:11] i dunno, hmm, maybe that just means more steps in the resolution of the name / path [15:14] you mea if the pvcreate had been done with a different path ? hm... [15:14] i dont know how names for pvs are done. [15:16] so yeah, th3e check that is uggested (pvs | grep) could be an issue. and result in not running pvresize. [15:16] but it seems the other pv commands when given a block device path probably open it, read the PV UUID and use *that* [15:19] just playing... i did a 'pvcreate' with the by-partuuid path: [15:19] pvcreate /dev/disk/by-partuuid/2079bb1d-d7ca-4b4f-a1d1-a62c06b7c570 [15:20] and then 'pvs' will show the pv with the 'loop5p1' name. I'm guessing that it just does effectively 'readlink -f' on whatever input for that. [15:25] thanks alot meena [15:26] now i'm back to being depressed about linux storage [15:54] s/linux storage/linux-lvm2 [16:17] i wish zfs would work somehow across computers,so you could build cloud storage [16:17] but chances are that then it simply wouldn't work [16:33] rharper: wrt sucking, i mean that wrt almost all of linux storage. its not limited to lvm. [16:39] imagine if ceph was easy! [18:00] it woudl still suck. [18:01] sorry.... rharper and I submitted a talk to open source summit, but it didn't get accepted. [18:02] things we learned and got burnedon in curtin and other places. [18:22] smoser: about storage on Linux? [18:22] did you still write it down? [18:26] https://hackmd.io/eMOklfSvS6aFCcmu_1h79Q [18:28] wow, this is literally the worst web page i've visited all day: http://www.golismero.com/ [18:28] smoser: cool! i … didn't expect that, but wow, cool! [18:44] uuids are not unique when you snapshot and re-attach. this goes for partition uuids, and fs uuids. What is a good way to find the right path to this thing. fstab ⬅️ wat [18:44] smoser: heh; lvm2 has a special place on my crap list ... [18:44] meena: https://wiki.ubuntu.com/FSTAB [18:46] consolidated list of best persistent links; we generally prefer to avoid FS_UUID if possible, as it;'s mutable; but in the absence of any other one, we use that [18:46] all that magic (like LABEL= or UUID=) it all works most of the time. [18:46] and when a human is typing stuff, the times ti doesn't work, they just live with and reboot or whatever. they say "oh well, that doesn't work because x y z" [18:50] i can copy/paste, or i can use human readable / writable paths.