I posted the following question:
I was quite surprised when two of my machines allowed me to follow
the update route when moving from SOL2.4 to 2.5.1. I think this is
the only time this has worked for me in the last 2 years of updates.
But one machine failed during the update with a complaint that /
was undersized. It reported / as being around 15Mb, which was
correct, but it was asking for around 35Mb which seemed awfully
big to me.
Sure enough, when I completed the "initial install" with all the
attendent headaches, I get the following from df:
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t3d0s0 33831 10439 20012 35% /
Does anyone know what happened or how to avoid this in the
future? I was having such fun doing updates and not complete
re-installs!!
*****************************************
Thanks to those that took the time to reply but nothing conclusive was
gathered. Their thoughts centered on the partitioning of the systems
but on both of the machines that allowed an upgrade, one had a single /
partition ( another plus for a single, large partition! ) while the
other had separate /, /var and /opt partitions. The machine with the
separate /, /var and /opt partitions was a server and the / partition
is 100Mb, var is 60Mb, and opt is 290Mb.
The reponses follow:
************************************************************
>From paul@icx.com Tue Jul 30 16:07 EDT 1996
I've seen similar results when doing a fresh install of Sol 2.5
Workstation (while Server install will give you two partions, roughly half
of the available disk space, minus the physical ram for swap). The install
will want to create a 'large' root partion of 90Mb(!!), but you can downsize
it to a smaller size. The 35Mb root partion could be for scratch/tmp
space for the installation process. When you are doing your update, is
your tmp it's own partion/fs or part of another?
************************************************************
From: djohnson@nbserv2.dseg.ti.com (Danny Johnson 0172547)
probably you do not have a separate /var partition.
the /var/sadm/ files can grow large, especially
/var/sadm/install/contents, which requires as much free
space as it is big since it is edited on the fly
during pkgadd's.
************************************************************
From: tim@ben.dciem.dnd.ca
May depend on just what separate partitions you have (or don't have.)
I took the SunOS -> Solaris Admin course and, while trying things out
in the install, I noted that it was asking for a huge / partition.
The reason was that either /var or /opt (or both) were not separate
partitions and so were going onto / making it rather large. Check the
system that failed to be "upgraded" and see if it doesn't have
/opt as separate while the other do.
************************************************************
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:06 CDT