Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SUBSYSFS11 Allocated Capacity full ...code108

Status
Not open for further replies.

himate

Technical User
Nov 14, 2002
20
GB
Hi all

I'm after advice based on some system alarms. Basically the Alarm 108 appears showing less than 5% free space on the Hard disc subfile system. I believe that it's due to the traffic reporting. See prints below;

<ALLOP;

CLASS: 3
108 FILE SYSTEM ROUTINE TEST ERROR
DATE TIME ALP NOIF EQU BRDID INF1 INF2
22DEC02 16:49:00 3 1 001-0-62-00 69 2 3

CLASS: 1

292 TRAFFIC RECORDING DATA DUMP COULD NOT BE EXECUTED
DATE TIME ALP NOIF UNIT INF1
22DEC02 17:32:01 4 1 2

293 TRAFFIC RECORDING INTERNAL MEMORY DATA ERASED - MEMORY FULL
DATE TIME ALP NOIF UNIT INF1
22DEC02 18:02:01 5 1 2

294 TRAFFIC RECORDING INTERNAL MEMORY DATA ERASED - MIDNIGHT DUMP
DATE TIME ALP NOIF UNIT INF1
23DEC02 00:11:00 11 1 2


END


<FISCP:IODEV=SYSDISK1;
FILE SYSTEM CAPACITY DATA
TOTAL DISK SPACE: 2069 MBYTES
SUBFS: SYSSUBFS11
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
51200 0 15000 /SYSN/USR1
SUBFS: SYSSUBFS21
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
51200 37439 15000 /SYSN/USR2
END


From the above print there is no available disc space on SYSSUBFS11. I also see that traffic reporting is running and cannot dump due to the disc capacity.

1)
Could the traffic reporting be causing the problem? If so what's the process for removing historical traffic records?

2)
What other processes can full up disc space?

This site has very small amounts of customer data entry and is VERSION=LZY2035118/1/R1A (bc9 I think)

thanks
 
Hallo,

I think, traffic-measurement is the reason.

With fiscp I can see, that no TM-SUBFS was created. Normally you make such a subfs with 5 or 10MB size. Then you can be sure, that the normal dump from MD will always work, because TM takes only this 5 or 10MB. Now you have the situation, that your traffic-measurement did fill your complete HDU until the end.

Now I recommend to printout your important TM-Data and then format partly the HDU:

bleqi:equ=1-x-xx-0

fimoe:subfs=syssubfs11;
fimoe:subfs=syssubfs21;

iosie:node=sysn,iodev=sysdisk1;
iosii:node=sysn,iodev=sysdisk1,sipos=3,subfs=syssubfs11&syssubfs21&tm-subfs;

fimoi:subfs=syssubfs21;

ficri:subfs=syssubf11,size=50;
fimoi:subfs=syssubfs11;

ficri:subfs=tm-subfs,size=10;
fimoi:subfs=tm-subfs,path=/sysn/usr1/acs/tm;

alrei;
gjrei;
hirei;
dusyi;

lalrl (my nickname, not the command to enter...)




 
Or if you don't like to create another subfile. You can just FIDIE:pATH=/SYSN/USR1/ACS/TM/*.*; be sure you take all TM data you need before you delete the files. This command will do if you don't like to disturb your REL1 or REL2. Using FIDIE will take you another year or two to do it again. Also if you format, you make the size 64; to max the space. //patcher
 
Perhaps the FIDIE command in combination with using the PDM application of DNA is the best and quickest way.
PDM retrieves the raw data on /sysn/usr1/acs/tm and stores it in the SQL server database. You may store for immediate reporting up to 18 months of TM data.

 
Thanks for your replies, much appreciated. Will go with the FIDIE command after discussions with the customer.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top