Avaya Support Forums  

Go Back   Avaya Support Forums > Contact Center Applications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 10-19-2011, 04:00 AM
soul0906 soul0906 is offline
Aspiring Member
 
Join Date: Aug 2010
Posts: 1
soul0906 has 10 reputation points
Default How to resolve filesystem full on CMS r12?

I have experienced filesystem full (%iused = 100%) as below. I have tried to remove a lot of garbage but it still become full soon.

# df -F ufs -o i
Filesystem      iused    ifree  %iused  Mount
/dev/dsk/c0t0d0s0  512000     0   100%  /
/dev/dsk/c0t0d0s3   1887   382113   0%  /cms

Other information as below:

# df -k
Filesystem       kbytes    used   avail   capacity Mounted on
/dev/dsk/c0t0d0s0   4130982 1260659  2829014   31%   /
/proc            0      0     0    0%   /proc
mnttab           0      0      0     0%   /etc/mnttab
swap         1112048      24  1112024    1%   /var/run
/dev/dsk/c0t0d0s3  3098743  269774   2766995    9%   /cms
swap         1112072     48  1112024    1%   /tmp

# uname -a
SunOS FT44430077 5.9 Generic_112233-11 sun4u sparc SUNW,Sun-Blade-100

# cat /etc/release
Solaris 9 4/03 s9s_u3wos_08 SPARC
Copyright 2003 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 25 February 2003
Reply With Quote
  #2  
Old 11-17-2011, 06:31 AM
kamra kamra is offline
Member
 
Join Date: Nov 2011
Location: India
Posts: 9
kamra has 10 reputation points
Default How to resolve filesystem full on CMS r12?

soul0906,

Infact its the inodes in the '/' or root filesystem which are completely consumed i.e. 100% used. The inodes or index nodes are used for any new file creation at the OS level and once all are used, not even temporary files get generated and your CMS becomes at risk of getting hung until some of the files are deleted. This issue in CMS generally crops up due to incorrectly configured alarm subsystem and related dependencies in CMS, which cause generation of 0 byte files at a regular interval and this may go on for years before the inodes get full.
There may be other reasons as well for a large number of file creation consuming the inodes. This is better looked by T3/backbone team in Avaya, if you have no prior experience with Solaris/Unix OS and CMS application with such issues.

Saurabh Kamra
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 04:02 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.