I was using freebsd-update to move to 9.2:
# freebsd-update -r 9.2-RELEASE upgrade
Ran through all the merging no problem, and then went to install:
# freebsd-update install
/: write failed, filesystem is full
install: ///boot/kernel/INS@bBbO: No space left on device
Kernel updates have been installed. Please reboot and run
"/usr/sbin/freebsd-update install" again to finish installing updates.
OMG! Rebooting would likely have been fatal at that point. And yes, my root FS was full:
olympia# df -k
Filesystem 1024-blocks Used Avail Capacity Mounted on
/dev/ad0s1a 507630 487372 -20352 104% /
devfs 1 1 0 100% /dev
procfs 4 4 0 100% /proc
/dev/ad0s1e 507630 18608 448412 4% /tmp
/dev/ad0s1f 34443364 1377450 30310446 4% /usr
/dev/ad0s1d 1469326 1057210 294570 78% /var
/dev/ad4s1d 946031670 820026292 50322846 94% /bigvol1
After cleaning up root (had some old kernels hanging around) and re-running the install everything was fine.
Since "freebsd-update install" knows how much space is needed for the new kernel, could it not check for adequate space up-front? (Same holds true for most other files, too.)
Ensure adequate disk space prior to running freebsd-install.
How-To-Repeat: Fill up root filesystem.
Run freebsd-update install.
See failures yet claims of success.
Over to maintainer.
For bugs matching the following criteria:
Status: In Progress Changed: (is less than) 2014-06-01
Reset to default assignee and clear in-progress tags.
Mail being skipped
Created attachment 201137 [details]
Add error message and exit for failing install.
This is probably because "install_files" does not captures errors when copying/installing files. This patch should update it to ensure these errors are caught and give users a potential remedy.
(In reply to Gerald Aryeetey from comment #3)
Seems reasonable to me; there is a typo in the error message, "BASEDDIR".
Created attachment 201139 [details]
FIXED Add error message and exit for failing install.
Updated patch to fix typo
Also this report is likely a duplicate of this one: bug #164131
*** Bug 164131 has been marked as a duplicate of this bug. ***
*** Bug 186278 has been marked as a duplicate of this bug. ***