Before you performed the upgrade did you run...
smcli cleanupd -mva
That command is not included in the documentation but is definetely a very important step that should be included. This cleans out the entire update repository. Now, I'm not sure if the updates live under /opt but I also upgraded from 1.3.3 to 1.3.4 recently at a customer and did not see this issue so I have to believe they do.
I had ran that command and it does actually detail it in the newer release notes that if you are concerned with space on the appliances to run that. However on my FSM appliance, the updates now live in /updateslib. I've attached the "du -k" output to clarify :
FSM-XXXXXXXXX:~ # df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vdb2 10079784 5015784 4551968 53% /
tmpfs 14137024 208 14136816 1% /dev
tmpfs 14137024 4 14137020 1% /dev/shm
/dev/vda1 1026776 40844 933772 5% /boot/dev/vdb3 30241636 25749192 2956248 90% /opt
/dev/vdb5 6048248 2789420 2951592 49% /var
/dev/vdb6 5043920 650712 4136988 14% /tmp
/dev/vdb7 23971336 16837968 5915676 75% /home
/dev/vdd1 82563600 5178192 73191424 7% /mirror0
/dev/vde1 123849912 988236 116570468 1% /dump/dev/vdf1 30959676 232028 29154988 1% /updateslib
So as you can see /opt on my FSM appliance is at 90% used, and this is where my real concern is. The FSM as it is now is working, but I am concerned with future updates, as the last update I installed wanted at least 4.8 GB free in order to proceed (and currently there is around 2.9 GB free).. I am open to any ideas to free up space... I've approached IBM about removing contents in /opt/ibm/director/proddata/updatedata/backup as this directory seems to contain a lot of backup versions of applications that are updated with each release, but don't seem to be removed, however IBM had no documented procedure for clearing this directory.
If that is the case I am not sure what level of code your Recovery Partition is running but I would advise requesting IBM send you the Recovery media for 1.3.4 so you won't need to do a series of upgrades to your FSM post rebuild. The caveat to that is if you have a recent backup of the FSM on 1.3.3 code, if this is the case then I would request the Recovery Media for 1.3.3 just to be sure your restore will work.
IBM are currently suggesting that we do a full reinstall of the FSM appliance from scratch and then reconfigure it from scratch as the only way to "reclaim" space in /opt. I was just wanting to see if anyone else had come up against this issue and had workarounds to get space back in /opt for re-use without having to do a full rebuild of the FSM from scratch. There is a bit of configuration in there currently that we don't want to have to redo again. IBM also stated that even a Backup of the appliance and then doing a recovery of the appliance to 1.3.4 and then restoring from the backup will still consume the same amount of space in /opt as the backup does indeed backup all of the /opt directory, so have ruled that out as a way to reclaim space.
Thanks for your help though. The suggestions did make perfect sense, although have been tried already