Similarly, I ran out of disk space … then quickly keyed Control-C to abort the upgrade, and so on.
I removed /boot/kernel.old, continued to move or remove other things e.g. /var/db/freebsd-update/*, it seems that:
- no matter how much I remove, the file system remains over capacity.
With the drive connected to a different computer:
root@mowa219-gjp4-8570p-freebsd:~ # df -ahT /dev/da3s2a
Filesystem Type Size Used Avail Capacity Mounted on
/dev/da3s2a ufs 3.4G 3.1G -18M 101% /tmp/nomadroot
root@mowa219-gjp4-8570p-freebsd:~ # cd /tmp/nomadroot
root@mowa219-gjp4-8570p-freebsd:/tmp/nomadroot # du -Ach -d 1 .
512B ./.snap
512B ./media
512B ./dev
13M ./rescue
7.4M ./sbin
2.1M ./var
244K ./libexec
512B ./tmp
512B ./mnt
512B ./proc
1.3M ./root
14M ./lib
4.0K ./nvidia
512B ./net
2.1M ./etc
240M ./boot
999M ./usr
1.3M ./bin
512B ./compat
2.9M ./usr.local.etc
1.8G ./uzip
1.5K ./unionfs
512B ./data
1.5M ./lost+found
3.1G .
3.1G total
root@mowa219-gjp4-8570p-freebsd:/tmp/nomadroot # cd && umount /tmp/nomadroot
root@mowa219-gjp4-8570p-freebsd:~ # lsblk da3
DEVICE MAJ:MIN SIZE TYPE LABEL MOUNT
da3 2:101 29G MBR - -
<FREE> -:- 993K - - -
da3s1 2:102 40M efi - -
da3s2 2:103 3.5G BSD - -
<FREE> -:- 1.0M - - -
da3s2a 2:105 3.5G freebsd-ufs label/nomadroot -
da3s3 2:104 25G BSD - -
<FREE> -:- 1.0M - - -
da3s3a 2:106 25G freebsd-ufs label/nomaddata -
<FREE> -:- 506K - - -
root@mowa219-gjp4-8570p-freebsd:~ #
For any of the listed folders, does disk usage appear excessive (compared to a fresh installation of NomadBSD)?
Is the output from df(1) sane in this case?
Can UFS not recover from (not regain free space after) over capacity situations?
TIA