[SERVER-23305] Seg Fault in devnull storage engine Created: 23/Mar/16  Updated: 06/Dec/22  Resolved: 28/Mar/16

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 3.0.7, 3.2.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: William Banfield Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File devfail.json     File devfail.playback    
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

Download the attached playback file
start a devnull storage engine
run mongoplay against the dev null storage engine with
./mongoplay play -p devfail.playback

The json file contains clearer information on the operations that cause the crash

Participants:

 Description   

A segmentation fault in the database causes crash. Occured when evergreen was using the storage engine as its backing mongod.



 Comments   
Comment by Ian Whalen (Inactive) [ 28/Mar/16 ]

Hey Will, devnull is not a supported storage engine so we don't plan on doing any work to fix these kinds of issues. If you believe that the segfault is independent of the storage engine for any reason, please feel free to reopen this issue and attach the stack trace as well as any other useful info.

Comment by William Banfield [ 23/Mar/16 ]

They're in the linked json file in a more readable format. I've also sent you a mongoplay binary so you can reproduce and see the stack trace

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