[SERVER-17767] Remove the code that ignores EBUSY returns from verify in the WT integration layer Created: 27/Mar/15  Updated: 03/Aug/18  Resolved: 11/Jun/18

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

Type: Improvement Priority: Major - P3
Reporter: Ramon Fernandez Marina Assignee: Sean Tao
Resolution: Won't Fix Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-26950 WiredTigerKVEngine::_salvageIfNeeded ... Closed
Gantt Dependency
has to be done after SERVER-17792 Shell doesn't close cursor when limit... Closed
Related
related to SERVER-16804 mongod --repair fails because verify(... Closed
Sprint: Storage NYC 2018-06-18
Participants:

 Description   

This change was a workaround for SERVER-16804. Now that SERVER-16804 has been fixed the workaround needs to be cleaned up.



 Comments   
Comment by Sean Tao [ 03/Aug/18 ]

Resolved as won't fix since WiredTiger still occasionally returns EBUSY, according to Michael Cahill, and therefore we still need this logic.

Comment by Sean Tao [ 05/Jun/18 ]

Here is the Evergreen patch:
https://evergreen.mongodb.com/version/5b16be582fbabe5abe90e510

We did get some errors, some of which I don't think are related to this patch, but this error also did pop up:
"errmsg" : "Salvage failed: 16: Device or resource busy",[js_test:read_committed_with_catalog_changes] 2018-06-05T17:17:30.269+0000 "code" : 8,[js_test:read_committed_with_catalog_changes] 2018-06-05T17:17:30.269+0000 "codeName" : "UnknownError",

...etc.

This is a bit concerning because salvage was originally not called for EBUSY errors, but the ticket said to ignore them, so possibly after we stopped ignoring the EBUSY error salvaged failed.

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