[Bug 250152] free space on rootfs on VM image is zero

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250152

            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 at FreeBSD.org
          Reporter: zebul666 at 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/Latest/
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 rootfs
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 test 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% with
a negative number of available blocks ?

-- 
You are receiving this mail because:
You are the assignee for the bug.