MongoDB with a WORM drive?

[kevin connors]

I am evaluating MongoDB as a solution to archiving a very large data set permanently.  In this solution, I will be using a WORM drive.  In my research and experimenting with MongoDB, it doesn't seem to naturally fit this scenario.  I saw this ticket that, I think, is focused on this problem: https://jira.mongodb.org/browse/SERVER-593.  It seems that no work has yet been done.  I was hoping to find a way to make the file system hosting "dbpath" completely read-only, or at least make the collections stored there readonly, but no luck.  Does anyone have any experience with this, or advice?

[Daniel Coupal]

The SERVER-593 ticket you refer to would be one step in the direction of being able to use a Write Once Read Many drive.

Once the above functionality is implemented, you could transfer a database to the drive, but you could not use the drive to create the initial database. I mean, you could not import data through MongoDB writing the documents only once. MongoDB does make use of internal tables to count documents in collections (among few internal operations) and those disk areas get re-written many times. So as long as you use the filesystem to copy your database to the WORM drive, then use MongoDB to read it, it would work.

But all the above is conditional to the SERVER-593 feature being implemented. At this point, the feature is not scheduled.