Hello managers,
We,ve just upgraded one of our dev machine from DEC OSF/1 3.2A to 3.2C
and are experiencing a VERY frustrating situation. Because of gcc
compile errors, we've decided to go back to 3.2A. This is NOT possible.
The system does not reconize anymore the ADVFS partitions tha were
locally installed on that machine.
Does anyone hace experienced the same problems ?
Can we go back to 3.2A other way then restoring backups on these
partitions ?
Detail of the upgrade :
1 - Clone the original disk :
Boot in single user mode
Zap label of destination disk
Use dd to clone the entire disk
dd if=/dev/rrz<source>c of=/dev/rrz<destination>c bs=1024k
(This trick is very usefull to test upgrades)
2 - Perform upgrade
Install the cloned disk on a different machine
Modify /etc/fstab to include only local disks
Use the installupdate command with a locally mounted cdrom
Install local mods to kernel and rebuild
3 - Test the newly upgrade disk
Properly shut down the systems
Install the 3.2C at the place of the 3.2A
Boot in single user
Restore original /etc/fstab
Boot in multi user
4 - Test the new 3.2c system
At this point no strange messges occured, and all of our apps
work fine.
We've experience problems with gcc version 2.6.3, and tryed to
recompile it. Errors occured that we don't have time to solve
now. Here is the compile errors :
...
touch stmp-int-hdrs
./xgcc -B./ -DIN_GCC -g -I./include -DNO_MEM -DNO_LONG_DOUBLE_IO
-O0 -I. -
c ./enquire.c
mips-tfile, /tmp/ccaawsfa.s:0 index 4294967295 is out of bounds for
lstrs, max i
s 0, mips-tfile.c line# 4642
*** Exit 1
Stop.
*** Exit 1
Stop.
The quick solution was to re-install the original 3.2A disk.
5 - Re-install original 3.2A disk
Properly shut down the system
Boot in multi-user
The system crash while trying to mount local ADVFS disks with
an error that looks like :
ADVFS exception in module ...
At this point the system keeps rebooting without generating
crash dumps (swap not initialize at that point)
The release notes does not specify that the ADVFS Metadata structure
changed (rel notes p. 4-11 item 4.4.2.4) but specify that you can
increase the Metadata Extent size (rel notes p. 4-12 item 4.4.2.10).
Does this means that section 4.4.2.4 should specify that there is a
change in the matadata structure in rel 3.2C ?
Thank's for your answers. I will summarize !
Michel Cyr
SIDOCI enr.
IST-Integration inc.
(514)252-4333 ex 258
Michel.Cyr_at_sidoci.qc.ca
Received on Thu Sep 28 1995 - 17:02:41 NZST