Bug 1659625

Summary:	Log how much space is being used in the boot.iso rootfs.img
Product:	Red Hat Enterprise Linux 8	Reporter:	Brian Lane <bcl>
Component:	lorax	Assignee:	Brian Lane <bcl>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Release Test Team <release-test-team>
Severity:	unspecified	Docs Contact:	Vladimír Slávik <vslavik>
Priority:	unspecified
Version:	8.0	CC:	atodorov, jwboyer
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	lorax-28.14.19-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-14 00:54:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Brian Lane 2018-12-14 20:22:35 UTC

The boot.iso rootfs that lorax creates defaults to 2G in size. It is hard to tell when it is almost full without downloading the image, mounting it, etc. So this adds running df on the rootfs after lorax installs all the files to it.

https://github.com/weldr/lorax/pull/551

Comment 5 Alexander Todorov 2019-02-06 10:42:56 UTC

From program.log:

Running... df /var/tmp/lorax.imgutils.fy3mki15
Filesystem     1K-blocks  Used Available Use% Mounted on
/dev/loop0       3397576 12036   3369156   1% /var/tmp/lorax.imgutils.fy3mki15
Return code: 0
Running... umount /var/tmp/lorax.imgutils.fy3mki15
Return code: 0
Running... losetup --detach /dev/loop0
Return code: 0