[SERVER-1132] Creating a database with slash in it causes 'file allocation failure' Created: 18/May/10  Updated: 12/Jul/16  Resolved: 18/May/10

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: 1.4.2
Fix Version/s: 1.5.2

Type: Bug Priority: Minor - P4
Reporter: Joakim Sernbrant Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MongoDB 1.4.2 CentOS 5.4


Participants:

 Description   

MongoDB shell version: 1.4.2
url: test
connecting to: test
type "help" for help
> use foo/bar
switched to db foo/bar
> db.foo.save({bar:1})
file allocation failure

That puts the server in a state where all new databases gives 'file allocation failure':

> use test
switched to db test
> db.foo.save({bar:1})
> use foo
switched to db foo
> db.foo.save({bar:1})
file allocation failure



 Comments   
Comment by auto [ 18/May/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: check for bad db names and don't segfault SERVER-1132
http://github.com/mongodb/mongo/commit/8cbcdcc9b6c6931943de09d427472a0d3662d3a9

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