[SERVER-32787]  WT_ERROR: non-specific WiredTiger error i cant restoring data with snapy Created: 19/Jan/18  Updated: 21/Mar/18  Resolved: 16/Feb/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.4.4
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Ahmet Inan Assignee: Mark Agarunov
Resolution: Incomplete Votes: 0
Labels: mongo, mongod, mongodb, restore, wiredtiger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

3.14.32-xxxx-grs-ipv6-64 #9 SMP Thu Oct 20 14:53:52 CEST 2016 x86_64 x86_64 x86_64 GNU/Linux Centos


Attachments: File COLLECTIONS.part1.rar     File COLLECTIONS.part2.rar     File COLLECTIONS.part3.rar    
Participants:

 Description   

When i try to restoring some datas from wiredTiger@2.7.0 i am taking un-explained erros like this,

"WT_SESSION.open_cursor: the process must exit and restart: WT_PANIC: WiredTiger lib rary panic
lt-wt: cursor open(table:collection-18--2919941413266653091) failed: WT_PANIC: WiredTiger library panic"
or like this;
"WiredTiger file: WT_ERROR: non-specific WiredTiger error"



 Comments   
Comment by Kelsey Schubert [ 16/Feb/18 ]

Hi inan.ahmet,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Regards,
Kelsey

Comment by Mark Agarunov [ 01/Feb/18 ]

Hello inan.ahmet,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide the complete log files from mongod, as well as the output you are seeing when trying to restore the data?

Thanks,
Mark

Comment by Mark Agarunov [ 19/Jan/18 ]

Hello inan.ahmet,

Thank you for the report. To get a better idea of what may be causing this, could you please provide the complete log files from mongod, as well as the output you are seeing when trying to restore the data.

Thanks,
Mark

Generated at Thu Feb 08 04:31:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.