Some folks out there are not reading the readme file before they update, and are running into trouble. Remember the "Important Safety Tip" line in Ghostbusters about not crossing the streams? This is kind of like that.
Have you cleaned up your OS drives lately?
It's important. You should do this every now and then, but especially before you do a big update, such as the update to Q3.4 (which may have you running multiple updates, as explained in my previous post)
You want to remove system updates that are getting old. You may want to keep the previous system software in order to roll back, but do you really need the one before that and the one before that? Are you really going to roll back your 7000 to the system code you used in September 2010? I doubt it. Don't be a hoarder. Delete it. Call Dr. Drew if you need to.
Then, let's check your analytic datasets. These can get big before you know it. If you leave them running all the time, even when you don't need to collect data, you're asking for trouble. Either only run them when you need to collect data (you can do this manually or via a script or alert), or for goodness sake export them as a .CSV file at the end of each month and delete them off the system so they don't get too large. There have been issues reported of problems with the systems once these files got much too large. Part of those issues have been addressed in Q3.4, but you still need to keep it clean.
Very bad things will happen if you let your OS drives fill up. Think of all the atoms of your body moving away from each other at the speed of light. Furthermore, when you do an update, the update will go much more smoothly if you clean up the OS drives, first.
See the readme section below, which I'm sure you forgot to read...
The following section comes from the Q3.4 readme file:
1.4 System Disk Cleanup
Remove any old unused Analytics datasets especially any over 2G in size. The following command can be used to list the datasets.
node:> analytics datasets show
DATASET STATE INCORE ONDISK NAME
dataset-000 active 745K 2.19M arc.accesses[hit/miss]
dataset-001 active 316K 1.31G arc.l2_accesses[hit/miss]
dataset-002 active 238K 428K arc.l2_size
dataset-003 active 238K 428K arc.size
dataset-004 active 1.05M 2.80M arc.size[component]
dataset-005 active 238K 428K cpu.utilization
Also remove old support bundles or old software updates. It's important that the system disk has at least 20 to 25 percent free space. The following commands can be used to compare the amount of free space to the system disk size. In this case, 289G free / 466G size = 0.62 or 62% free space, which is reasonable. If you have trouble getting enough system disk free space call Oracle Support.
node:> maintenance system disks show
profile = mirror
root = 4.44G
var = 14.3G
update = 1.12G
stash = 1.38G
dump = 131G
cores = 29.7M
unknown = 15.0G
free = 289G
DISK LABEL STATE
disk-000 HDD 1 healthy
disk-001 HDD 0 healthy
node:> maintenance hardware select chassis-000 select disk select disk-000 show
label = HDD 0
present = true
faulted = false
manufacturer = SEAGATE
model = ST95000NSSUN500G
serial = 9SP123EQ
revision = SF03
size = 466G
type = data
use = system
device = c2t0d0
interface = SATA
locate = false
offline = false