[Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

[Dave Jones]

@noahod I've just tried this with the current
https://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/jammy-preinstalled-server-arm64+raspi.img.xz image
(downloaded today) and with just your growpart config (I didn't try the
resize_rootfs key), the card booted without resizing the rootfs:

  ubuntu at ubuntu:~$ df -h /
  Filesystem      Size  Used Avail Use% Mounted on
  /dev/mmcblk0p2  3.3G  2.2G  964M  70% /

  ubuntu at ubuntu:~$ sudo fdisk -l /dev/mmcblk0
  Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0xc34fdafd

  Device         Boot  Start     End Sectors  Size Id Type
  /dev/mmcblk0p1 *      2048  526335  524288  256M  c W95 FAT32 (LBA)
  /dev/mmcblk0p2      526336 7656787 7130452  3.4G 83 Linux

Could you have a go with just the growpart config?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-image in Ubuntu.
https://bugs.launchpad.net/bugs/1947311

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
    mode: off
    devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions