Mongo Exception mmapv1

[f0rch0s3]

I had recently problems with low disc space on my machine so I decided to reduce the size of the journals, therefore I put 

mmapv1:

smallFiles: true

However, I receive this error every time when I try to restart mongo with the new changes. (Without these settings in the mongo.conf file, it works fine). Could you please tell me what could be the problem and how I can solve it? 

 sudo -u mongod mongod --journal

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten] MongoDB starting : pid=8056 port=27017 dbpath=/data/db 64-bit host=Unknown-44-6d-57-73-86-ab

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten] db version v3.2.1

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten] git version: a14d55980c2cdc565d4704a7e3ad37e4e535c1b2

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1k-fips 8 Jan 2015

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten] allocator: tcmalloc

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten] modules: none

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten] build environment:

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten]     distmod: rhel70

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten]     distarch: x86_64

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten]     target_arch: x86_64

2016-02-11T22:31:57.475+0000 I CONTROL  [initandlisten] options: { storage: { journal: { enabled: true } } }

2016-02-11T22:31:57.509+0000 I -        [initandlisten] Detected data files in /data/db created by the 'mmapv1' storage engine, so setting the active storage engine to 'mmapv1'.

2016-02-11T22:31:57.509+0000 W -        [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty.

2016-02-11T22:31:57.516+0000 I JOURNAL  [initandlisten] journal dir=/data/db/journal

2016-02-11T22:31:57.517+0000 I JOURNAL  [initandlisten] recover begin

2016-02-11T22:31:57.517+0000 I JOURNAL  [initandlisten] info no lsn file in journal/ directory

2016-02-11T22:31:57.517+0000 I JOURNAL  [initandlisten] recover lsn: 0

2016-02-11T22:31:57.517+0000 I JOURNAL  [initandlisten] recover /data/db/journal/j._0

2016-02-11T22:31:57.553+0000 I JOURNAL  [initandlisten] recover cleaning up

2016-02-11T22:31:57.553+0000 I JOURNAL  [initandlisten] removeJournalFiles

2016-02-11T22:31:57.634+0000 I JOURNAL  [initandlisten] recover done

2016-02-11T22:31:57.635+0000 I JOURNAL  [initandlisten] preallocating a journal file /data/db/journal/prealloc.0

2016-02-11T22:32:00.173+0000 I -        [initandlisten]   File Preallocator Progress: 943718400/1073741824 87%

2016-02-11T22:32:13.433+0000 I JOURNAL  [durability] Durability thread started

2016-02-11T22:32:13.433+0000 I JOURNAL  [journal writer] Journal writer thread started

2016-02-11T22:32:13.466+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'

2016-02-11T22:32:13.466+0000 I NETWORK  [HostnameCanonicalizationWorker] Starting hostname canonicalization worker

2016-02-11T22:32:13.466+0000 I NETWORK  [initandlisten] waiting for connections on port 27017

2016-02-11T22:32:14.002+0000 I FTDC     [ftdc] Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost. OK

2016-02-11T22:32:14.023+0000 W FTDC     [ftdc] Uncaught exception in 'UnknownError Caught std::exception of type boost::filesystem::filesystem_error: boost::filesystem::file_size: No such file or directory: "/data/db/diagnostic.data/metrics.interim.temp"' in full-time diagnostic data capture subsystem. Shutting down the full-time diagnostic data capture subsystem.

[Asya Kamsky]

When you remove this option, does MongoDB come up clean?  No errors or warnings in the logs?

Asya

--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
 
For other MongoDB technical support options, see: http://www.mongodb.org/about/support/.
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user...@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/b92bba01-ba59-4757-bcb7-6a9bbc6f73db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Asya Kamsky
Lead Product Manager
MongoDB
Download MongoDB - mongodb.org/downloads
Free MongoDB Monitoring - cloud.mongodb.com
Free Online Education - university.mongodb.com
Get Involved - mongodb.org/community
We're Hiring! - https://www.mongodb.com/careers