[SERVER-2012] drop fails when unable to allocate Created: 27/Oct/10  Updated: 06/Dec/22  Resolved: 14/Sep/18

Status: Closed
Project: Core Server
Component/s: MMAPv1, Storage
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-3606 Dropping an index fails when quota ex... Closed
is duplicated by SERVER-8989 Cannot drop db when filesystem is full Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

Create a new database and collection in a fresh dbpath, and fill it up. Then try to drop it - there is a file allocation exception.

Probably related to allocating the freelist namespace.

We should also check:

  • hitting quota limit
  • dropping an index instead of a ns


 Comments   
Comment by Justin Smestad [ 23/Mar/11 ]

This could be something related to my ticket about pre-allocation errors and capped collections: http://jira.mongodb.org/browse/SERVER-2818

Generated at Thu Feb 08 02:58:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.