Summary: Root cause of swap space full

[Meg Wall]

Hi Managers,

I've got only 4 replies, I'm still not very sure what the root cause
was. It's hard to do forensic analysis when the problem can't be
repeated. (well, thank goodness). Thanks for all of you! Here's what
I've got:

From: Andrew_Cordova 

The only way I could see that this particular file system causing the
crash would be if it had not been mounted. If you had say 4 disks, two
active  w/2 mirrors.   /weblogs is mounted from active disk 2 and for
some reason it is offline. what you have now is  just the /weblogs
mount point, w/ no disk mounted under it. 

The app is stupid, it just writes to where it is told, which is
/weblogs, which in this scenario is just the mount point w/ no
underlying disk.  if /weblogs was full, then effectively / is full. 
just as if /home was not a separate file system and a user was to fill
it up, then again, w/o quotas enabled, they have filled /. 

i have not seen this scenario w/ a fs created on rootdg, but have seen
it when a datadg mount that we had lost the disk, the app just kept
writting to /mountpoint till it ran us out of space. /tmp eventually
runs out of space because it is effectively part of / and you have a
down system, reboot clears /tmp - you login and clean space. 

an unusual scenario for sure, but as you know in this business the
unusual is the norm. one other item to chk is that if / is still
unusually full, then you may have /weblogs mounted over the data still
written under /weblogs the mount point.