Teamsite Caching

libra

Hi

Today morning the file system size in our teamsite production server was about 90 % To reduce the space consumption, we did a clean up and we removed one of the project branch, After this removal there space was almost the same, there was not much change.


Now the interesting thing, is after 1 hr, there was huge reduction in the file system size.
Suddenly dropped to 86% /opt/iwoven/iw-store



So my question, is there any caching or anything happening behind the screen,
I have gone through the post about caching (ON/Off /.iwmnt ) and in that here was a word about flush frequency ,I am not sure wther it caused it or not.
Please help and clarify the issue.


My teamsite server is
Interwoven TeamSite 6.7.1 Service Pack 1 OS 2.6.9-55.ELsmp i386 GNU/Linux
Thanks in advance..

Warm Regards
libra

Adam Stoller

Hi Today morning the file system size in our teamsite production server was about 90 % To reduce the space consumption, we did a clean up and we removed one of the project branch, After this removal there space was almost the same, there was not much change. Now the interesting thing, is after 1 hr, there was huge reduction in the file system size. Suddenly dropped to 86% /opt/iwoven/iw-store So my question, is there any caching or anything happening behind the screen, I have gone through the post about caching (ON/Off /.iwmnt ) and in that here was a word about flush frequency ,I am not sure wther it caused it or not. Please help and clarify the issue. My teamsite server is Interwoven TeamSite 6.7.1 Service Pack 1 OS 2.6.9-55.ELsmp i386 GNU/Linux Thanks in advance.. Warm Regards libra

Removal of a branch takes time - the UI and/or file system interface return control to you long before the operation is actually complete - you can run iwstat -c to see what's going on in the background.

However - you might try running iwfsshrink first - since you might be able to get a significant reduction in disk space utilization without having to sacrifice branches of content to do so - you could also consider a second store ($$) on a different partition and use iwmigrate to transfer branches to the second store (use iwfsshrink on the second store afterwards as iwmigrate tends to cause lots of duplicate data).