Hi,
I'm trying to track down why image installs still aren't being trimmed. It was implemented in lorax, and also the buildvm's in Fedora infra are using qemu discard=unmap, so it should just work (it works locally with virtio block devices, the virt-manager default).
Workstation Live x86 koji logs includes
https://kojipkgs.fedoraproject.org//packages/Fedora-Workstation-Live/Rawhid…
Which shows
2022-07-22 00:41:33,905 INFO: Running... fstrim -v /mnt/sysimage/
2022-07-22 00:41:34,113 INFO: /mnt/sysimage/: 2.1 GiB (2205618176 bytes) trimmed
2022-07-22 00:41:34,113 DEBUG: Return code: 0
That's expected. However, it's no smaller than several weeks ago when discards weren't passing through from guest buildervm to the host with the sparse file. I'm still pondering how to track down how we can get a return code of 0, and yet the trim didn't actually do anything.
Next, two examples of oz logs:
https://kojipkgs.fedoraproject.org//packages/Fedora-Cloud-Base/Rawhide/2022…https://kojipkgs.fedoraproject.org//packages/Fedora-Workstation/Rawhide/202…
But fstrim isn't mentioned, so I'm suspicious oz isn't including all the anaconda logs, which would be an oz bug.
--
Chris Murphy
Hi!
We are planning an extensive clean-up of the code for the Installation
Source spoke to prepare the code for the payload modularization. That
creates a good opportunity for revisiting the design of the user interface
as well. We would like to address some of the long-term issues and propose
an alternative. It shouldn't be anything drastic, just a small
reorganization of the current components and options.
See the proposal at https://github.com/rhinstaller/anaconda/discussions/4257
for more information.
Vendy