|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|
|||
Upgrade -> disk full!
I have three machines running -current, and I apply new snapshots fairly recently. Two of them run through the upgrade process without a hitch. On the third machine, the disk fills up every time!
I boot bsd.rd, hit "upgrade", select sd0 as the root disk, etc etc. As soon as it starts extracting sets, /dev/rd0a fills up. It's like the upgrader is extracting them to the ramdisk, rather than sd0. What could cause this? Last edited by beavers; 15th February 2018 at 08:32 PM. Reason: typo |
|
|||
That's exactly where I discovered that /dev/rd0a is the partition that's filling up. All of the partitions on sd0 are mounted correctly on /mnt during the upgrade, it's just that the sets aren't extracting to them -- they're writing to the ramdisk partition (/dev/rd0a), which is only lik e 3.6mb or something, so it fills up almost immediately. When it happens, df shows the other partitions haven't moved at all.
|
|
||||
It still would make things easier if you can show us, some real details,
the output of 'df -h' would be a good starting point, there just is not enough details to say anything.
__________________
My best friends are parrots |
|
|||
Sure thing. Here's `df -h` right before extracting the sets:
Code:
Filesystem Size Used Avail Capacity Mounted on /dev/rd0a 3.5M 3.1M 317K 91% / /dev/sd0a 1005M 462M 492M 48% /mnt /dev/sd0k 40.0G 266M 37.8G 1% /mnt/home /dev/sd0d 3.9G 12.0K 3.7G 0% /mnt/tmp /dev/sd0f 2.0G 1.0G 865M 55% /mnt/usr /dev/sd0g 1005M 184M 770M 19% /mnt/usr/X11R6 /dev/sd0h 8.6G 676M 7.5G 8% /mnt/usr/local /dev/sd0j 2.0G 2.0K 1.9G 0% /mnt/usr/obj /dev/sd0i 2.0G 2.0K 1.9G 0% /mnt/usr/src /dev/sd0e 8.7G 15.9M 8.3G 0% /mnt/var /dev/sd4a 5.3T 799G 4.3T 15% /mnt/storage Code:
Filesystem Size Used Avail Capacity Mounted on /dev/rd0a 3.5M 3.5M 1.0K 100% / /dev/sd0a 1005M 462M 492M 48% /mnt /dev/sd0k 40.0G 266M 37.8G 1% /mnt/home /dev/sd0d 3.9G 12.0K 3.7G 0% /mnt/tmp /dev/sd0f 2.0G 1.1G 797M 58% /mnt/usr /dev/sd0g 1005M 184M 770M 19% /mnt/usr/X11R6 /dev/sd0h 8.6G 676M 7.5G 8% /mnt/usr/local /dev/sd0j 2.0G 2.0K 1.9G 0% /mnt/usr/obj /dev/sd0i 2.0G 2.0K 1.9G 0% /mnt/usr/src /dev/sd0e 8.7G 15.9M 8.3G 0% /mnt/var /dev/sd4a 5.3T 799G 4.3T 15% /mnt/storage |
|
||||
Thank you. I'm going to guess that it is not the tiny ramdisk that is filling up, as there isn't ever much space within -- but rather, your relatively small /usr partition.
You are attempting to upgrade -current. And, in the 2017/11/05 entry of the Following -current FAQ, it says: Quote:
|
|
|||
I would have suspected the same thing, except after receiving all the "device is full" messages, df shows /usr still has 797M free. It's definitley writing to the ramdisk, rather than /usr.
For the past few weeks I have instead been following the (not-recommended) directions at http://www.openbsd.org/faq/upgrade62.html#NoInstKern, and that works fine. No disk space issues whatever. (Also, fwiw, /usr/share/compile does not exist on this system.) |
|
|||
Quote:
Other than this missing directory (which would affect KARL certainly, but I can't imagine how it could affect extracting the sets), I honestly have made very few modifications to any of these systems. Each has a single disk, auto-partitioned the way the disklabel(8) suggests. |
|
|||
Code:
~$ dmesg | head -1 OpenBSD 6.2-current (GENERIC.MP) #6: Tue Feb 13 20:16:11 MST 2018 |
|
|||
Quote:
Code:
/storage/www/htdocs/pub/OpenBSD/snapshots/amd64 -> /6.2/amd64 /sys -> usr/src/sys /var/tmp -> ../tmp |
|
|||
Quote:
Code:
/: write failed, file system is full tar: Failed write to file ./var/www/bin/ping: No space left on device tar: Failed write to file ./var/www/bin/traceroute: No space left on device tar: Could not create: ./var/www/cache: No space left on device tar: Could not create: ./var/www/cgi-bin: No space left on device tar: Unable to create ./var/www/conf: No space left on device Code:
$ ls -AlF /var lrwxr-xr-x 1 www www 12 Mar 8 2017 /var/www@ -> /storage/www $ grep storage /etc/fstab /dev/sd4a /storage ffs rw,nodev,nosuid 1 2 At any rate, I rebooted bsd.rd, created /storage on the ramdisk, then mounted sd4a there, and the upgrade proceeded as expected. Woohoo! TL;DR -- I am a newb, and jggimi very astutely diagnosed my goofy mistake. Thank you immensely for your assistance! |
|
|||
Where can I find a copy of the upgrade script? (I don't know how to pull it out of bsd.rd. )
|
|
||||
The install and upgrade scripts are both symbolic links to install.sub, the source to that script is in src/distrib/miniroot/install.sub. There are also architecture stubs with machine dependent bits located in src/distrib/<arch>/<varies>/install.md.
Here's a link to the -current install.sub at this time, revision 1.1060: http://cvsweb.openbsd.org/cgi-bin/cv...ype=text/plain |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Full Disk Encryption | jjstorm | OpenBSD Installation and Upgrading | 3 | 30th May 2016 08:19 PM |
Full disk encryption in NetBSD 7.0 RC2 | bashrules | NetBSD Installation and Upgrading | 1 | 18th August 2015 02:11 AM |
Reliability concerns on full disk encryption | virtuvoos | OpenBSD Security | 4 | 31st October 2013 11:06 PM |
FreeNAS 8.3.1 introduces full disk ZFS encryption | J65nko | News | 0 | 22nd March 2013 02:54 AM |
Full disk encryption with Loop-AES | deviant085 | OpenBSD Security | 9 | 23rd November 2009 12:51 AM |