|
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.
|