nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Diskspace issue

HeMan10

Hi,
We have TeamSite 6.5 with Search running on a Solaris 8 box. Backing store is under one partition and TeamSite is installed in another partition. Each partition is 36GB. The partition on which TeamSite is installed is running out of diskspace very fast. Currently its at 78%. Couple of days back it was around 60%. Deleting the log files didn't help a bit. Theres a directory named proc and a du -k againt it returns 16615190(16 Gig). My guess is the search agent is doing that. Does any one know which process creates that directory? Appreciate any help.

Thanks
-H

Find more posts tagged with

Comments

HeMan10

Ok. It seems that Proc is a virtual directory it doesn't occupy any disk space at all. Back to square one. I am clueless as to why the disk is 79% full. All the box has is TeamSite and Search. I deleted the log files to see if that makes any difference. But it didn't help at all. Any ideas please?

Thanks,
-H

nipper

go to the Unix shell. cd to the root dir

run du -s *

That will tell the #blobks per dir.

Can narrow it down from there

Event subsystem is a good candidate

me

Adam Stoller

go to the Unix shell. cd to the root dir

run du -s *

That will tell the #blobks per dir.

Can narrow it down from there

Event subsystem is a good candidate

me

slight variation:

/> du -k -s /* | sort -n

will list sizes in kilobytes instead of blocks and the output will be sorted so that the directories containing the largest amount of data will appear at the bottom. Note, however, that this operation may take a fair amount of time depending on the size of your disk and such.

Also - you should run the command as root (directly or via sudo) or elase you're likely to get a lot of warnings about files and/or directories that you don't have permissions for and the results will be incomplete.

HeMan10

Nipper and Ghoti,
Thanks for your replies. I executed the command to check the size in each directory of iw-home and evensubsystem was the culprit. Couldn't believe my eyes when I saw a file as large as 14GB. Everything is normal now after getting rid of the flat file and setting it up to use MySQL database. I also I had another issue with memory on the box. TeamSite used to come down every now and then with low virtual memory warning. Not sure if this fix, resolves the memory issue also. The server has 4 Gigs of memory. Appreciate any pointers.

Thanks again,
-H