[SERVER-35607] No such file or directory src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 267 Created: 14/Jun/18  Updated: 04/Sep/18  Resolved: 18/Jun/18

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

Type: Bug Priority: Major - P3
Reporter: Damien Pereira Assignee: Nick Brewer
Resolution: Done Votes: 0
Labels: envns, rdi, rpu, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: Linux
Participants:

 Description   

After a disk problem the server has shutdown and cannot be restart.

When I try to start I get the following logs:

2018-06-14T20:03:18.179+0000 I CONTROL [initandlisten] MongoDB starting : pid=6 port=27017 dbpath=/data/db 64-bit host=6aa3f69ecb52
2018-06-14T20:03:18.180+0000 I CONTROL [initandlisten] db version v3.4.1
2018-06-14T20:03:18.180+0000 I CONTROL [initandlisten] git version: 5e103c4f5583e2566a45d740225dc250baacfbd7
2018-06-14T20:03:18.180+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1t 3 May 2016
2018-06-14T20:03:18.180+0000 I CONTROL [initandlisten] allocator: tcmalloc
2018-06-14T20:03:18.181+0000 I CONTROL [initandlisten] modules: none
2018-06-14T20:03:18.181+0000 I CONTROL [initandlisten] build environment:
2018-06-14T20:03:18.181+0000 I CONTROL [initandlisten] distmod: debian81
2018-06-14T20:03:18.181+0000 I CONTROL [initandlisten] distarch: x86_64
2018-06-14T20:03:18.181+0000 I CONTROL [initandlisten] target_arch: x86_64
2018-06-14T20:03:18.181+0000 I CONTROL [initandlisten] options: {}
2018-06-14T20:03:18.397+0000 W - [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty.
2018-06-14T20:03:18.434+0000 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-06-14T20:03:18.440+0000 W STORAGE [initandlisten] Recovering data from the last clean checkpoint.
2018-06-14T20:03:18.458+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=3477M,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2018-06-14T20:03:18.573+0000 I - [initandlisten] Assertion: 28595:2: No such file or directory src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 267
2018-06-14T20:03:18.581+0000 I STORAGE [initandlisten] exception in initAndListen: 28595 2: No such file or directory, terminating
2018-06-14T20:03:18.581+0000 I NETWORK [initandlisten] shutdown: going to close listening sockets...
2018-06-14T20:03:18.581+0000 I NETWORK [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2018-06-14T20:03:18.581+0000 I NETWORK [initandlisten] shutdown: going to flush diaglog...
2018-06-14T20:03:18.581+0000 I CONTROL [initandlisten] now exiting
2018-06-14T20:03:18.582+0000 I CONTROL [initandlisten] shutting down with code:100



 Comments   
Comment by Nick Brewer [ 15/Jun/18 ]

Hi damien.pereira

Unfortunately, if the WiredTiger.turtle file is that badly corrupted, it's not possible to perform a repair. That file provides the metadata that is used to interpret the WiredTiger.wt file, which in turn is used to interpret all other .wt files.

For future reference, here's some precautions you can take to mitigate issues related to unreliable storage layers or server failures:

Nick

Comment by Damien Pereira [ 15/Jun/18 ]

Hi Asya,

We have an empty WiredTiger.turtle file with a 0 size.

Do you think it could be repaired?

Comment by Asya Kamsky [ 15/Jun/18 ]

Looks the same version and symptoms as SERVER-28168 could you check the contents of the dbpath and the sizes of the files there?

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