From owner-freebsd-bugs@freebsd.org Tue Oct 6 07:30:26 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EB84A42ADED for ; Tue, 6 Oct 2020 07:30:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4C58JL5zs9z45NM for ; Tue, 6 Oct 2020 07:30:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id CBC6642B229; Tue, 6 Oct 2020 07:30:26 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CB85642ADEC for ; Tue, 6 Oct 2020 07:30:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C58JL50p0z45NL for ; Tue, 6 Oct 2020 07:30:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8BCC3232BB for ; Tue, 6 Oct 2020 07:30:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 0967UQHj071155 for ; Tue, 6 Oct 2020 07:30:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 0967UQxU071154 for bugs@FreeBSD.org; Tue, 6 Oct 2020 07:30:26 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 250152] free space on rootfs on VM image is zero Date: Tue, 06 Oct 2020 07:30:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: zebul666@hotmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2020 07:30:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250152 Bug ID: 250152 Summary: free space on rootfs on VM image is zero Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: zebul666@hotmail.com The available free space in the rootfs of the VM images found in https://download.freebsd.org/ftp/releases/VM-IMAGES/12.1-RELEASE/amd64/Late= st/ are zero. I tested the qcow2 image and the VMDK image and it's the same, so I except = it to be true for the VHD image too. Once the qcow2 VM image is booted in qemu/kvm on Linux, on gets: # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/gpt/rootfs 3044988 2933380 -131988 105% / devfs 1 1 0 100% /dev And the kernel is spitting in console message about no space in rootfs, like freebsd kernel: pid 802 (dd), uid 2 inumber 162985 on /: filesystem full These images are dynamically allocated, meaning that if you add +5Gb to the rootfs, the resulting growth size of the image is almost null. So there is no trade-off to increase the rootfs size. I except it to be a better experience to have a non null free space on root= fs when trying freeBSD or using it with a VM. This is non trivial task to increase the VM image size, increase the rootfs partition, and finally grow the fs in rootfs. Unless this is meant as a tes= t of your knowledge... This voids the ease of use of a VM image, though. As a side note, isn't there a bug in `df` that reports a capacity of 105% w= ith a negative number of available blocks ? --=20 You are receiving this mail because: You are the assignee for the bug.=