[SERVER-28630] Mongo zero size db folder is not clear on the disk Created: 05/Apr/17  Updated: 05/Apr/17  Resolved: 05/Apr/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.2 Required
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: eric_huang Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operate System: CentOS 6.3 2.6.32-642.13.1.el6.x86_64


Issue Links:
Duplicate
duplicates SERVER-22985 Allow dropDatabase to accept flags to... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Hi There,

We using Mongo DB 3.2.6 to store log information, and store the log in db by its persistent time. After we drop the expired database, the database will not show by command "show dbs". The database folder size is zero, and it is still exist on the disk.
Why the db.dropDatabase() cannot purge the zero folder on the disk?

========================
106M diagnostic.data
300M journal
72K local
64K _mdb_catalog.wt
4.0K mongod.lock
84K sizeStorer.wt
4.0K storage.bson
0 TrackingLogDB_2016121700_2017031700
0 TrackingLogDB_2016121800_2017031800
0 TrackingLogDB_2016121900_2017031900
0 TrackingLogDB_2016122000_2017032000
0 TrackingLogDB_2016122100_2017032100
0 TrackingLogDB_2016122200_2017032200
0 TrackingLogDB_2016122300_2017032300
0 TrackingLogDB_2016122400_2017032400
0 TrackingLogDB_2016122500_2017032500
0 TrackingLogDB_2016122600_2017032600
0 TrackingLogDB_2016122700_2017032700
0 TrackingLogDB_2016122800_2017032800
0 TrackingLogDB_2016122900_2017032900
0 TrackingLogDB_2016123000_2017033000
0 TrackingLogDB_2016123100_2017033100
0 TrackingLogDB_2017010100_2017040100
0 TrackingLogDB_2017010200_2017040200
0 TrackingLogDB_2017010300_2017040300
0 TrackingLogDB_2017010400_2017040400
3.7M TrackingLogDB_2017010500_2017040500
3.7M TrackingLogDB_2017010600_2017040600
3.7M TrackingLogDB_2017010700_2017040700
3.6M TrackingLogDB_2017010800_2017040800
3.5M TrackingLogDB_2017010900_2017040900
========================

Regards
Eric Huang



 Comments   
Comment by Michael Cahill (Inactive) [ 05/Apr/17 ]

eric_huang, this is covered in SERVER-22985. Please vote for that issue to indicate that you would like it addressed.

Generated at Thu Feb 08 04:18:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.