neuralnode
Technical User
Hi all,
I have recently performed software update on AIX 5.3L via fast path smit maintain_software, choosing: Service Update Management Assistant --> Download Updates Now --> Download Maintenance Level. My current ML was 5300-00, and I chose 5300-03.
The update began and lasted for a few hours. The process was installing software from the hard disk, as I didn't insert any CD or tape. (I don't think it connected with some IBM repository on its own, but correct me if I'm wrong.) I would think that since the update used files that were already stored on the disk there shouldn't be much to install. But since it eventually used up A FEW HUNDRED MB of the /usr filesystem, my assumption had, evidently, been wrong. During the update process I had to increase the /usr filesystem size, and now it's 4GB. I didn't note down how much of additional space it took up, but I'd say about 600-800MB.
My further assumption was that the system must have unpacked some compressed filesets and didn't by itself remove the older ones (i.e. those being replaced), so that's why I had /usr crammed with all that data. Still, it seemed a bit too much.
Next, I went again to smit maintain_software and chose "Clean Up Software Images in Repository". This indeed freed some space, but only about 200MB or so.
My question is: What the hell did I do? Why so much space? How can I find out where the upgrade fixes are stored, or whether there are any duplicates left?
Next I checked oslevel -r and it showed 5300-00, not 5300-03, I guess because the package "devices.common.IBM.sni.rte.1.2.0.7.bff" failed during the update, which was evident from the smit log. I therefore downloaded that fileset with all dependent update fixes from IBM, and installed them via smit update_all.
Now oslevel -r (after a reboot) shows 5300-01. I would expect 5300-03.
In smit.log all new updates seem sucessfully commited, e.g.:
bos.rte.libpthreads 5.3.0.30 USR COMMIT SUCCESS
Remark: I had commited - just in case - all existing software prior to the entire procedure, and then after the procedure too. Smit answered in both cases that there was nothing to commit.
Some of the newly installed fixes are in 5300-04 ML, and so 5300-04 shows up as an option in "Download Maintenance Level" in Service Update Management Assistant.
So now I'm totally confused. I understand the whole situation like this: I started updating ML from 5300-00 to 5300-03, but one update fileset wasn't found on the hard disk, so the ML remained at 5300-00. Then I installed this missing update with all required dependencies. The ML went to 5300-01. The question is: Why not to 5300-03?? How can I check what is missing and should be installed so that oslevel -r finally shows 5300-03?
As you have noticed, I'm a newbie in this respect, so I'd appreciate some enlightened mind explain the above and answer my questions.
Thanks in advance.
I have recently performed software update on AIX 5.3L via fast path smit maintain_software, choosing: Service Update Management Assistant --> Download Updates Now --> Download Maintenance Level. My current ML was 5300-00, and I chose 5300-03.
The update began and lasted for a few hours. The process was installing software from the hard disk, as I didn't insert any CD or tape. (I don't think it connected with some IBM repository on its own, but correct me if I'm wrong.) I would think that since the update used files that were already stored on the disk there shouldn't be much to install. But since it eventually used up A FEW HUNDRED MB of the /usr filesystem, my assumption had, evidently, been wrong. During the update process I had to increase the /usr filesystem size, and now it's 4GB. I didn't note down how much of additional space it took up, but I'd say about 600-800MB.
My further assumption was that the system must have unpacked some compressed filesets and didn't by itself remove the older ones (i.e. those being replaced), so that's why I had /usr crammed with all that data. Still, it seemed a bit too much.
Next, I went again to smit maintain_software and chose "Clean Up Software Images in Repository". This indeed freed some space, but only about 200MB or so.
My question is: What the hell did I do? Why so much space? How can I find out where the upgrade fixes are stored, or whether there are any duplicates left?
Next I checked oslevel -r and it showed 5300-00, not 5300-03, I guess because the package "devices.common.IBM.sni.rte.1.2.0.7.bff" failed during the update, which was evident from the smit log. I therefore downloaded that fileset with all dependent update fixes from IBM, and installed them via smit update_all.
Now oslevel -r (after a reboot) shows 5300-01. I would expect 5300-03.
In smit.log all new updates seem sucessfully commited, e.g.:
bos.rte.libpthreads 5.3.0.30 USR COMMIT SUCCESS
Remark: I had commited - just in case - all existing software prior to the entire procedure, and then after the procedure too. Smit answered in both cases that there was nothing to commit.
Some of the newly installed fixes are in 5300-04 ML, and so 5300-04 shows up as an option in "Download Maintenance Level" in Service Update Management Assistant.
So now I'm totally confused. I understand the whole situation like this: I started updating ML from 5300-00 to 5300-03, but one update fileset wasn't found on the hard disk, so the ML remained at 5300-00. Then I installed this missing update with all required dependencies. The ML went to 5300-01. The question is: Why not to 5300-03?? How can I check what is missing and should be installed so that oslevel -r finally shows 5300-03?
As you have noticed, I'm a newbie in this respect, so I'd appreciate some enlightened mind explain the above and answer my questions.
Thanks in advance.