-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Critical - P2
-
None
-
Affects Version/s: 2.2.1
-
Component/s: None
-
None
-
Linux
-
None
-
None
-
None
-
None
-
None
-
None
-
None
I have a mongod node which is using much more disk space than stored object space. On Wednesday, I --repair'd the database, which brought the storageSize down to ~dataSize, now storageSize is back to 44x the dataSize!
In this case, dataSize is ~480Mb, storageSize is ~21Gb, and there are ~24Gb of database files.
> db.stats()
{
"db" : "dbname",
"collections" : 8,
"objects" : 4729,
"avgObjSize" : 101896.2233030239,
"dataSize" : 481867240,
"storageSize" : 21079039904,
"numExtents" : 39,
"indexes" : 11,
"indexSize" : 1332688,
"fileSize" : 25204097024,
"nsSizeMB" : 16,
"ok" : 1
}
I'll attach some python code that reproduces the problem.
- duplicates
-
SERVER-2958 Freelist algorithm causes storage fragmentation
-
- Closed
-