mongorestore V3 - don't know what to do with file

2,181 views
Skip to first unread message

Neville Franks

unread,
Mar 20, 2015, 12:44:34 AM3/20/15
to mongod...@googlegroups.com
I'm getting an error using Mongorestore with the current Mongo V3 Release as follows:

-------------
c:\webapps\clibu\bat>C:\MongoDB\Server\3.0\bin\mongorestore -v  \webapps\clibu\dumps\local_bkp\Clibu-nevf
2015-03-20T12:11:34.426+1100    using write concern: w='1', j=false, fsync=false, wtimeout=0
2015-03-20T12:11:34.428+1100    building a list of dbs and collections to restore from \webapps\clibu\dumps\local_bkp\Clibu-nevf dir
2015-03-20T12:11:34.429+1100    don't know what to do with file "\webapps\clibu\dumps\local_bkp\Clibu-nevf\articles.bson", skipping...
2015-03-20T12:11:34.429+1100    don't know what to do with file "\webapps\clibu\dumps\local_bkp\Clibu-nevf\articles.metadata.json", skipping...
....
-------------

This is on Windows V8. I've also tried 

C:\MongoDB\Server\3.0\bin\mongorestore -v -d Clibu-nevf \webapps\clibu\dumps\local_bkp

and get "don't know what to do with subdirectory ..."

I've tried running mongod with both with and without --storageEngine wiredTiger and get the same error.

I've tried everything I can think of without success.

I'm trying to convert Mongo V2.6 db's to Mongo V3 WiredTiger.

If I use mongorestore V2.6 on the same dump it works correctly and all data appears to have been imported and working correctly using WiredTiger.

Neville Franks

unread,
Mar 24, 2015, 3:03:02 AM3/24/15
to mongod...@googlegroups.com
I've just setup a CentOS server and installed Mongo V3. I've done a mongodump from another server running Mongo V2.6 and when I use mongorestore on the CentOS server I get the same errors: "don't know what to do with file xyz.bson" etc. 

The V3 MongoDB is using WiredTiger in case that is relevant.

Neville Franks

unread,
Mar 24, 2015, 3:45:23 AM3/24/15
to mongod...@googlegroups.com
I've finally been able to get something working. If I run just 'mongorestore' in the parent of the 'dump' directory it works. Either I'm doing something stupid or mongorestore is broken in V3.


On Friday, 20 March 2015 15:44:34 UTC+11, Neville Franks wrote:
Reply all
Reply to author
Forward
0 new messages