70 Gigs of lost space???

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

rex007can

70 Gigs of lost space???

Postby rex007can » Fri Feb 22, 2008 5:38 pm

Here's my problem.
I have Scalix Corporate 10.0.3. I'm upgrading to 11 in a few weeks.
But that's beside the point.

My problem is, I have 135Gigs of space in my /var volume.
Right now, it says that I have 118Gigs of space used up.
Almost all of this is used up by the scalix folder under /var/opt/scalix
Which is where the mailboxes are, so it's okay.

Where I lose it is, the total amount of space taken up by adding all my mailboxes comes to about 52Gigs. This is confirmed by both adding individual mailbox sizes from the SAC, and by checking the size of the Data folder under /var/opt/scalix/Data
If I count all the other sub-folders in the Scalix folder, it will come out to a few gigs, no more that 4Gigs.
See screenshots
Image

Image
So my question is, where is the missing <60> Gigs?
The mailboxes are 52, but the system's telling me that 118 are used? What could be taking so much wasted space??


I also noticed that I have 11 gigs of files in the tmp and temp folders, some of which are over 2 years old.
Like
-rw-rw-rw- 1 root scalix 598 Jan 8 2007 pop.3879.bas9-montreal02-1096615536.dsl.bell.ca.15915
-rw-rw-rw- 1 root scalix 519 Dec 2 2006 pop.3879.bas9-montreal02-1096615546.dsl.bell.ca.4562
-rw-rw-rw- 1 root scalix 519 Dec 2 2006 pop.3879.bas9-montreal02-1096615546.dsl.bell.ca.4566
-rw-rw-rw- 1 root scalix 519 Jan 27 2007 pop.3879.bas9-montreal02-1096615548.dsl.bell.ca.20172
-rw-rw-rw- 1 root scalix 519 Jan 27 2007 pop.3879.bas9-montreal02-1096615548.dsl.bell.ca.20174
-rw-rw-rw- 1 root scalix 519 Jan 27 2007 pop.3879.bas9-montreal02-1096615548.dsl.bell.ca.20176
-rw-rw-rw- 1 root scalix 519 Jan 27 2007 pop.3879.bas9-montreal02-1096615548.dsl.bell.ca.20178
-rw-rw-rw- 1 root scalix 519 Jan 27 2007 pop.3879.bas9-montreal02-1096615548.dsl.bell.ca.20180
-rw-rw-rw- 1 root scalix 519 Jan 27 2007 pop.3879.bas9-montreal02-1096615548.dsl.bell.ca.20182
-rw-rw-rw- 1 root scalix 519 Jan 27 2007 pop.3879.bas9-montreal02-1096615548.dsl.bell.ca.20184
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22174
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22176
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22178
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22180
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22182
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22184
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22186
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22188
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22190
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22192
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22194
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22196
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22198
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22200
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22202
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22204
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22206
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22208
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22210
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22212
-rw-rw-rw- 1 root scalix 598 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22214
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22216
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22218
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22220
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22222
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22224
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22226
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22228
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22230
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22232
-rw-rw-rw- 1 root scalix 598 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22234
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22236
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22238
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22240
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22242
-rw-rw-rw- 1 root scalix 519 Feb 12 2007 pop.3879.bas9-montreal02-1096615561.dsl.bell.ca.22244

What the hell??

Valerion
Scalix Star
Scalix Star
Posts: 2730
Joined: Thu Feb 26, 2004 7:40 am
Location: Johannesburg, South Africa
Contact:

Postby Valerion » Mon Feb 25, 2008 3:56 am

Run a few omscan -A -a -f -x runs and see if that helps. omscan is responsible for clearing out orphans and files in ~tmp and ~temp. If you want you can delete everything in ~tmp and ~temp anyway, as long as the server is not actively running. Just to a omtidyallu -M afterwards (you will need to do this for the upgrade anyway).

After your omscans, see if there's anything in ~orphans. Usually there's also a period orphans are kept in the data directory before being moved to ~orphans, and another period before they get deleted.

rex007can

Postby rex007can » Mon Feb 25, 2008 7:51 am

I ran omscan just 2 weeks ago.
I will look for the ~orphan as suggested, thanks.

Now what about that 11Gigs of stuff, some pretty old, in tmp and temp?

Valerion
Scalix Star
Scalix Star
Posts: 2730
Joined: Thu Feb 26, 2004 7:40 am
Location: Johannesburg, South Africa
Contact:

Postby Valerion » Mon Feb 25, 2008 8:30 am

If the server is not running (after omshut) you can delete tmp and temp's contents. Never do this while the server is active though. Just do a omtidyallu -M after.

rex007can

Postby rex007can » Mon Feb 25, 2008 8:41 am

Will do.
Thank's a lot.

rex007can

Postby rex007can » Mon Feb 25, 2008 11:40 am

One more question, that nobody's ever answered me clearly.

Is there an issue with running 2 servers in the same structure, but one at 10 and the other at version 11?

I know the clients arent compatible.
But I'm going to update a server at a remote office first, and I want to make sure there wont be any issues with the server at the main office, which I will update 2 weeks later.


Return to “Scalix Server”



Who is online

Users browsing this forum: Google [Bot] and 3 guests

cron