[SERVER-2460] conflict between durability journal directory and database 'journal' directory in directoryperdb mode Created: 01/Feb/11  Updated: 06/Dec/22  Resolved: 20/Dec/18

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

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

MongoDB shell version: 1.8.0-rc0-pre-
connecting to: test
> use journal;
switched to db journal
> db.c.save( {} );
> db.dropDatabase();

{ "dropped" : "journal", "ok" : 1 }

>

Tue Feb 1 14:26:35 [conn1] dropDatabase journal
Tue Feb 1 14:26:35 [conn1] removeJournalFiles
Tue Feb 1 14:26:35 [dur] couldn't open /data/db/journal/lsn errno:2 No such file or directory
Tue Feb 1 14:26:35 [dur] warning: open of lsn file failed
Tue Feb 1 14:26:35 [dur] warning exception opening journal file couldn't open file /data/db/journal/j._1 for writing errno:2 No such file or directory
Tue Feb 1 14:26:35 [dur] exception in durThread causing immediate shutdown: couldn't open file /data/db/journal/j._1 for writing errno:2 No such file or directory
Tue Feb 1 14:26:35 Got signal: 6 (Abort trap).

Abort trap



 Comments   
Comment by Dwight Merriman [ 04/May/11 ]

let's disallow new databases with the name journal always - that way they don't exist if you switch to journaling later. just say it's a reserved one?

or, disallow journal with directory per db always

if you have existing, and this combination is not present, we can still allow, to avoid legacy problems, and just block new creation.

Comment by Eliot Horowitz (Inactive) [ 02/Feb/11 ]

we should disallow dbs with the name journal with dur on and db per directory

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