- 
    Type:Bug 
- 
    Resolution: Duplicate
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: 2.2.1
- 
    Component/s: None
- 
    None
- 
    Environment:Linux
- 
        ALL
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
The documentation for --directoryperdb seems to suggest that this is supported.
$ ps -C mongod -f | grep directoryperdb
ubuntu   15776     1  0 Dec20 ?        00:00:07 mongod --fork --logpath mongod.log --directoryperdb
$ mount | grep /data/db
/dev/xvdg on /data/db/foo type ext4 (rw,noatime)
$ mongo
MongoDB shell version: 2.2.1
connecting to: test
> use foo
switched to db foo
> db.c.insert({})
> db.dropDatabase()
{
	"errmsg" : "exception: delete data files with a directoryperdb caught exception exception: boost::filesystem::remove: Device or resource busy: \"/data/db/foo\"",
	"code" : 14043,
	"ok" : 0
}
> 
- related to
- 
                    SERVER-1379 dropdb with directoryperdb should remove contents, not delete directory (mmapV1) -         
- Closed
 
-