Tonight I attempted to upgrade a 2.6 FCS U1/170E to 2.6 5/98 and ran into
a problem. I'd like to know if my conclusion about the problem I had is
correct before I tried to upgrade once again. Here's the story:
In order to know if the 2.6 -> 2.6 5/98 would work fine, I first
tried it on the old 9GB (holding /, /usr, /var, /usr/local, /opt) - The
machine was upgraded last week to a 18GB, which meant I could simply
remove the 18gb and use the 9gb to test the upgrade (nothing had changed
since the machine went 9gb -> 18gb so both disks' contents was identical).
That upgrade test went fine and less than 5 files were saved out by the
upgrade with a ":2.6" extension.
Then I re-inserted the 18gb disk and re-booted from the cdrom and
proceeded to the very same questions that I had answered before ( for the
test). The upgrad started and around the end of the upgrade process, the
console started to display messages about FS "/a" (c0t0d0s0) being full.
The 256mb "/" (mounted as /a) had become full. After a reboot in order to
get the machine back in working order, I discovered that the solaris
upgrade process had created a "/usr" in the "/" slice, filling it up as it
tried to upgrade the OS.
In short, when the upgrade started, it had:
then, when it saved the modified files (*:2.6) it became:
/a/usr/opt (c0t0d0s5) stale mount since /usr was renamed.
/a/usr/local (c0t0d0s6) stale mount since /usr was renamed.
So when the upgrade dumped the packages, it dumped them in c0t0d0s0 under
a new /usr directory instead of dumping them under c0t0d0s4.
I fixed this by restoring / and /var (not /usr since it had been spared)
** My temporary conclusion:
When we upgraded from 9gb to 18gb, the "/usr" directory on c0t0d0s0 might
have been created with wrong permissions or the "root" of the c0t0d0s4
slice (/usr) might have had something different than root:sys with 0775.
It's likely that one or the other might have been root:root with 0755.
The upgrade process realized that and renamed it before going on. This
explains when the test upgrade on the 9gb went fine while the final
upgrade on the 18gb failed. Does anyone agree with this? I'd like to know
before the upgrade is attempted once again.
PS: Please CC me by email if you, thank you.. :)
,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~* They cannot scare me with their empty spaces
Vincent S. Cojot, Computer Engineering. STEP project. _.,-*~'`^`'~*-,._.,-*~
Ecole Polytechnique de Montreal, Comite Micro-Informatique. _.,-*~'`^`'~*-,.
Linux Xview/OpenLook resources page _.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'
Between stars - on stars where no human race is
I have it in me so much nearer home
To scare myself with my own desert places. - Robert Frost
They cannot scare me with their empty spaces