Contentstore far larger than expected

[srowsell]

I'm looking to upgrade the local environment that I use for development – I have to install the recent security update – and in preparation for this I'm making a copy of the database and contentstore.  Again, this is a development environment; I have imported maybe 1 or 2 GB of files, and looking around using Share or Explorer I can't see very much content.

Windows reports that the size of the contentstore directory is 135GB.

I know that no one reading this will have specific knowledge of my system about what might cause this, but is there a good general answer?

I'm running 4.1.6 Enterprise, by the way, and it's just a simple local installation.

Steve

[mrogers]

Very strange.   Can you use windows to see where windows thinks the content is used up?

[srowsell]

I have now done so.  As you know, the contentstore is divided up, so I'll try to represent it below.  Working on the assumption that the name of the files is based on its nodeRef – and I don't know whether or not that's a valid assumption – I plugged that into the node browser to see if it can be found, and no, it can't.  (In other words, one of the files at the bottom of this file structure was 0a6d4a30-58ee-4999-bf46-d33e0266ac02.bin, so I plugged "workspace://SpacesStore/0a6d4a30-58ee-4999-bf46-d33e0266ac02" into the node browser and did a noderef search, and had no results.)

I then did a search based on the date that these nodes entered the system (which was January 24, 2014) and tried this query:

@cm:created:["2014-01-24T00:03" TO "2014-01-25T11:04"]

No results in the node browser (using workspace://SpacesStore, and fts-alfresco).

Now it's not quite true that I haven't been putting some content into this environment.  I've put a fair bit in, but it's in the process of testing, so it all gets deleted fairly quickly.  I wouldn't have thought that there was 100+GB worth overall, but anyway it isn't there now.

<ul>
<li>2013, 6.7GB</li>
<li>2014, 118GB</li>
<ul>
<li>1, 118GB</li>
<li>2, 1.92GB</li>
<ul>
<li>2</li>
<li>3</li>
<li>6</li>
<li>7</li>
<li>8</li>
<li>9</li>
<li>14</li>
<li>15</li>
<li>16</li>
<li>17</li>
<li>20</li>
<li>21</li>
<li>22</li>
<li>24, 97.5GB</li>
<ul>
<li>9</li>
<li>10</li>
<li>11</li>
<li>14, 1.14GB</li>
<li>15, 64.3GB</li>
<ul>
<li>54 folders, each with 400MB to 1.2GB, each of which contain a number of binary files between 700 and 800 KB</li>
</ul>
<li>16, 32.1GB</li>
</ul>
<li>27, 19.3GB</li>
<li>28</li>
<li>29</li>
<li>30</li>
</ul>
</ul>
</ul>

[mrogers]

No its not a node ref.

So that all looks like valid content.

Perhaps the nodes are still being held in the trash can or the version store after you have deleted them?  

Also make sure the content store cleaner is running.

[mrogers]

No its not a node ref.

So that all looks like valid content.

Perhaps the nodes are still being held in the trash can or the version store after you have deleted them?  

Also make sure the content store cleaner is running.

[srowsell]

I looked a few things up, perhaps this will be useful.
- the trash can is empty
- repository.properties had these settings: system.content.eagerOrphanCleanup=false, and system.content.orphanProtectDays=14
- I just changed these settings to "true" and "1", respectively, but that might be closing the barn door after the horse has already left.

Is there a way to manually run the cleaner?  I suppose I could just delete the orphans myself, but I think that using the cleaner would give a better brand of confidence.  Alternatively, is there a way to check if it's actually being run?  I suppose the logs should give some hint of it, but I can find no mention of the sequence of characters "clean" in the alfresco.log.

Steve