Uploaded image for project: 'MongoDB Database Tools'
  1. MongoDB Database Tools
  2. TOOLS-943

AssertionException when trying to restore fs.chunks collection (GridFS) using mongorestore

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.1.9
    • Component/s: mongodump, mongorestore
    • Environment:
      Linux Ubuntu trusty (14.04)
    • Needed

      _mongorestore_ fails to restore a dump containing a collection called "fs.chunks" (used by [GridFS][1]).

      It looks like the chunks in this collection are too big (~32MB).

      $ mongorestore <exportDataDestination>
      ...
      Failed: my_db.fs.chunks: error restoring from my_dump/my_db/fs.chunks.bson: insertion error: EOF

      Logs:

      015-10-15T17:05:28.766+0000 I - [conn36] Assertion: 10334:BSONObj size: 33545165 (0x1FFDBCD) is invalid. Size must be between 0 and 16793600(16MB) First element: insert: "fs.chunks"
      2015-10-15T17:05:28.772+0000 I CONTROL [conn36] 0x127b4a2 0x121c0e4 0x1208cd8 0x1208d8c 0x9754db 0xb6cde8 0x9c88bd 0xc63aa5 0xc662c0 0x9528ad 0x1228755 0x7f95c49d4182 0x7f95c470147d
      ----- BEGIN BACKTRACE -----
      ...
      ----- END BACKTRACE -----
      2015-10-15T17:05:28.773+0000 I NETWORK [conn36] AssertionException handling request, closing client connection: 10334 BSONObj size: 33545165 (0x1FFDBCD) is invalid. Size must be between 0 and 16793600(16MB) First element: insert: "fs.chunks"

      Notes:

      • Mongo version: 3.1.9
      • Dump was generated using mongodump tool (no error/warning during creation, mongo version was 3.0.7)
      • Restoration seems to work fine on all other collections

      [1]: http://docs.mongodb.org/manual/reference/gridfs/#gridfs-chunks-collection

            Assignee:
            gabriel.russell@mongodb.com Gabriel Russell (Inactive)
            Reporter:
            nicolaspanel Nicolas Panel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: