Mini tutorial for extend a qemu image

on

flatpak install flathub org.gnome.Platform//3.26

I run out of space. How should I extend the size?

changed the description

My steps to extend qemu:

$ qemu-img resize -fraw qemu_x86_64.img +1G
#get into qemu
$ sudo apt-get install parted
$ sudo parted
resizepart ...
quit
$ sudo resize2fs /dev/sda2

Is this worth to add to docs?

This might be something we should add to the docs (since it's much faster and easier than manually running the image-builder script with whatever qcow2 size). If we add this though, I'd like to give explicit steps for the "resizepart ..." because not everyone will know what to do.

Sure, I can do ASCII screen captures or image captures

My only concern is: in order to mimic the device kit, is there a max size limit to honor?

I see this as HowDoI or FAQ

Well I'd add the qemu resize info to the mini-tutorials or additional tutorials (not sure what the difference is there).

The question of a max size limit to honor is going to be a common one and I am working on an FAQ which this would be a great addition to, but we don't have an answer to the max size yet.

changed title from Installing flatpak runtime qemu image runs out of space to Mini tutorial for extend a qemu image

Ok, mini tutorial then

See image-builder#8 (closed)

Additionally there's no reason why we wouldn't want to make the qemu image larger, it's only for the SD card that we don't want to write all zeros:

image-builder#9 (closed)

• Enter parted:

purism@pureos:~$ sudo parted
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.

• Show free avaliable space:

(parted) print free                                                       

Model: ATA QEMU HARDDISK (scsi)
Disk /dev/sda: 6821MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
        32,3kB  1049kB  1016kB           Free Space
 1      1049kB  191MB   190MB   primary  ext4         boot
 2      191MB   3600MB  3409MB  primary  ext4
        3600MB  6821MB  3221MB           Free Space

• Resize partition 2:

(parted) resizepart 2

Warning: Partition /dev/sda2 is being used. Are you sure you want to continue?

• As we are expanding disk there's no risk. Accept:

Yes/No? Yes

• Choose the end of free avaliable space:

End?  [3600MB]? 6821                                                      

• Exit parted:

(parted) quit                                                             

Information: You may need to update /etc/fstab.

• Resize filesystem:

purism@pureos:~$ sudo resize2fs /dev/sda2

resize2fs 1.44.3 (10-July-2018)
Filesystem at /dev/sda2 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 1
The filesystem on /dev/sda2 is now 1618691 (4k) blocks long.

• Check new avaliable space:

purism@pureos:~$ df -h

S.ficheros     Tamaño Usados  Disp Uso% Montado en
udev             481M      0  481M   0% /dev
tmpfs             99M   724K   99M   1% /run
/dev/sda2        6,1G   2,5G  3,4G  43% /
tmpfs            495M      0  495M   0% /dev/shm
tmpfs            5,0M      0  5,0M   0% /run/lock
tmpfs            495M      0  495M   0% /sys/fs/cgroup
/dev/sda1        172M    44M  116M  28% /boot
tmpfs             99M   1,3M   98M   2% /run/user/1000

mentioned in issue image-builder#8 (closed)

After adding cloud-initramfs-growroot to the image (see image-builder!39 (merged)) then all a user needs to do on a fresh image is to sudo resize2fs /dev/vda2 and I can add this to the current docs.

mentioned in issue #44 (closed)

I'm using https://arm01.puri.sm/job/Images/job/Image%20Build/279/

using the .xz image

I still need to do:

unxz image

$ qemu-img resize -fraw qemu-x86_64.img +1G

# run qemu image (I see cloud-initramfs-growroot expanding to free space)

# get into qemu

$ sudo resize2fs /dev/sda2

Is it an option to add resize2fs to sudo without password and add

sudo resize2fs /dev/sda2

to the initial commands for purism session?

I'm not sure if this tutorial is needed anymore

See

image-builder#8 (comment 2906)

someone just needs to send in a patch that runs the resize2fs and disables the systemd unit afterwards.

Wait I thought we (by we I mean me :)) were just going to document the resize2fs step. I just haven't gotten to it yet so sorry bout that but will soon.

I just point out that resize2fs is a low level step that we should keep away from normal user. Is that possible?

yes, we have automatic resizing during first boot, @albfan if that doesn't work for you let us know.

closed