Disk Space Issue

[Shravan K]

The percent of disk space used for /opt/quovadx/qdx5.3 is more than or equal to 80.I’m getting an Alert with the message above .

1.I’ve tried to do some clean up work by using “hcidbinit -AC”,and remove all the junk data present.

2.Before this i cleaned up shared memory and semaphores by using

the commands ipcs…then… ipcrm -m [shmid]….ipcrm -s [semid]

3.even then i couldn’t address my issue successfully rather

it gave birth to new problem I’m unable to parse the message from inbound thread to outbound.Intresting point is i dont see any errors populated in error logs and even in logs i dont find anything related to that operation.i dont see any messages in error database or recovery database.when i checked for pending messages i find few.

Did anyone experienced this before?

could anyone address my issue 🙁

Thanks

Shravan

Topic

[John Hamilton]

What OS are you on?

I’m guesing AIX.

Do a df and find the file system with usage greater the 80 %.

You could also change the alerts to not alert for that  but the engine has some built in things that once a disk is so full it will shutdown until you clean things up.

You could also just make the file system larger if it just too small.

[Robert Milfajt]

If you are running AIX, you need to find out which files are filling up your file system.  The best way I found to do this is:

find <> -type f -exec du -ka {} ; | sort -n

for <>, plug in the directory you want to search, in this case, /opt/quovadx/qdx5.3.

You may also want to redirect the output of the command to a file or pipe it to less or more (remember less is more)!

The result will be a list of files with the largest ones at the head of the list.  Start looking at the real big files and if they are process logs or SMAT files, you can start making decisions on whether you need to purge or add disk space.

Good luck and hope this helps,

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Jim Kosloskey]

Shravan,

If you are not already recycling and archiving your SMAT and Log files you need to get that set up to happen routinely.

Also, sometimes we turn up the Engine ‘noise’ level in the NetMonitor and forget to turn it back down – that will create very large logs quickly.

Check your NetConfig(s) to ensure the noise level is set appropriately for your use.

Remeber the NetConfig setting happens at startup, the NetMonitor settings are ‘temporary’ – meaning you change on the fly – but you need to remember to turn it off as well.

If you have all of the above in place and still have issues, it might be time to start thinking about acquiring more space.

I would not recommend turning off the system alerts. If you are multiple site you only need them active in one site. A John indicated they are your early warning something bad is going on and are intended to give you time to rectify the situation before emergency handling is forced by Cloverleaf(R).

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Author]

Replies