Sundar Yamunachari wrote: > This is not exactly package size. Each release comes with a file that > says how much space is needed for the file systems. The upgrade code > reads from a file and adds a overhead. It will then include the size > of the files those will be preserved during the upgrade. So there is > no control during the upgrade. You can delete or move some of the > files to create more space for upgrade. Can you try upgrade with 35 gb > free space and see whether the upgrade is successful. >>
OK, success. I did better then 35 gb. As you can see below I managed to increase the free disk space to 58.5 gb. So now one has to think. Originally when I tried to install snv116 it complained: Disk c1t2d0s0 / Existing 185524 (MB) Required 195147 (MB) If I read in between the lines, existing hard disk space is 181 gb and required is hard drive space 190 gb. The difference is 9 gb. the space I had left was 24 gb. So 24 gb + 9 gb = 31 gb. The install required 31 gb. What takes up that much space? Is it stored packages so I can back out? What should I delete to prevent it from building up? 31 gb is an awfully large required space for an upgrade. As you can see below I managed to increase the free disk space to 58.5 gb. Any way, I'm glad I'm running snv116 now. I hope the new installer does a better job, at least to let me know why it requires so much space and suggest how to reduce the requirement. Thanks for your help Paul $ df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t2d0s0 187100276 123803445 61425829 67% / >> >> $ df -k >> Filesystem kbytes used avail capacity Mounted on >> /dev/dsk/c1t2d0s0 187100276 159734811 25494463 87% /
