[SERVER-16639] Server restart with WiredTiger on full disk causes a segfault Created: 22/Dec/14  Updated: 23/Jan/15  Resolved: 20/Jan/15

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.8.0-rc3
Fix Version/s: 3.0.0-rc6

Type: Bug Priority: Minor - P4
Reporter: Robert Guo (Inactive) Assignee: Susan LoVerso
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File wt-files-st.txt     Text File wt-st-3.txt     Text File wt-st-4.txt    
Backwards Compatibility: Fully Compatible
Operating System: OS X
Steps To Reproduce:

1. Create 1GB ramdisk: diskutil erasevolume HFS+ 'RAM Disk' `hdiutil attach -nomount ram://2000000`
2. start mongod with wiredTiger (default setting, except dbpath)
3. create some random 100MB binary files with: dd if=/dev/urandom of=file bs=1048576 count=100
4. insert them using mongofiles until disk is full and the server crashes
5. run df to determine the amount of free space left on the ramdisk
6. run: dd if=/dev/urandom of=file bs=xxxxx count=1 in the ramdisk directory, where bs= the free space from step 5. This should fill up the ramdisk completely.
7. restart the server and connect mongo
8. segmentation fault 11

stack trace is attached

Participants:

 Description   

Trying to restart a wiredTiger mongod after it has been terminated due to a full disk causes a segfault



 Comments   
Comment by Robert Guo (Inactive) [ 20/Jan/15 ]

assembly of __wt_write

Comment by Robert Guo (Inactive) [ 16/Jan/15 ]

LLDB stack trace

Comment by Michael Cahill (Inactive) [ 15/Jan/15 ]

sue, can you please take a look at this one? From the stack trace, it might be something simple?

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