mongodb - tokumx数据库恢复失败的问题

Question

不好意思，虽然知道这里是mongodb的版块，自己使用的是tokumx，但网上查了下tokumx跟mongodb其实相同的，所以只能够在这里请教问题了。

手上有个站群网站程序，使用的是tokumx的数据库，数据库大概有600多万的数据量，最近因为服务器不稳定所以想搬迁数据库，使用的了dump的备份命令，用mongorestore恢复的时候，一直遇到错误没有能够恢复成功，遇到的问题如下：

每次恢复到一定程序的时候，会出现以下错误信息：

INVALID OBJECT - going try and pring out
size: 3077
name : _id 18
_id: 1495819
name : body 2
body: "
<h1>Fix ajscaxs2m75.js
error</h1>
<p>ajscaxs2m75.js
Description :</p>
<p>ajscaxs2m75.js
is a process from unknown product, unknown co..."
name : cahegoryidA 18
cahegoryidA: 7138414316591513600
Mon Oct 10 13:03:34.102 Assertion: 10320:BSONElement: bad type 111
0xe86096 0xad16bd 0xacd88c 0x6ceba7 0x719983 0x6d6ec0 0x6d6d6b 0x6d6d6b 0x6d8b03 0x71a09e 0x6af30d 0x6aeb2d 0x7fda07542b45 0x6c8b32
mongorestore(_ZN5mongo15printStackTraceERSo+0x26) [0xe86096]
mongorestore(_ZN5mongo10logContextEPKc+0xfd) [0xad16bd]
mongorestore(_ZN5mongo11msgassertedEiPKc+0x9c) [0xacd88c]
mongorestore(_ZNK5mongo11BSONElement4sizeEv+0x197) [0x6ceba7]
mongorestore(_ZN5mongo8BSONTool11processFileERKN5boost10filesystem4pathE+0x5c3) [0x719983]
mongorestore(_ZN7Restore9drillDownEN5boost10filesystem4pathEbbb+0x1170) [0x6d6ec0]
mongorestore(_ZN7Restore9drillDownEN5boost10filesystem4pathEbbb+0x101b) [0x6d6d6b]
mongorestore(_ZN7Restore9drillDownEN5boost10filesystem4pathEbbb+0x101b) [0x6d6d6b]
mongorestore(_ZN7Restore5doRunEv+0x613) [0x6d8b03]
mongorestore(_ZN5mongo8BSONTool3runEv+0x18e) [0x71a09e]
mongorestore(_ZN5mongo4Tool4mainEiPPc+0x6cd) [0x6af30d]
mongorestore(main+0x2d) [0x6aeb2d]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fda07542b45]
mongorestore() [0x6c8b32]
assertion: 10320 BSONElement: bad type 111

换了3台服务器，在相同的debian 64位系统下都一样的错误，开始怀疑原来的数据库出问题了，想尝试利用robomongo工具连接数据库来删除，但现在遇到的问题是，数据库是可以连接，网站都正常打开，但利用robomongo连接后搜索或者删除代码想删除ajscaxs2m75.js 这篇文章，发现返回的信息都是相同的错误代码assertion: 10320 BSONElement: bad type 111，请问这种情况怎样解决？

Answer 1

I can’t solve the problem you encountered, but I think it is necessary to explain some problems.
First of all, MongoDB and TokuMX are two companies. The latter is independently maintained and operated by forking the community version of MongoDB 2.4, and has no direct connection with MongoDB. Although most of the commands are still the same, the internal mechanism is very different. So asking questions about tokumx in the mongodb forum is likely to get no answers.
Besides, there are not many users using TokuMX. Now this company has been acquired by Percona due to operational problems. If you want professional help, you can ask Percona for help.