[SERVER-1724] Repair halts with segmentation fault Created: 03/Sep/10 Updated: 12/Jul/16 Resolved: 03/Sep/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 1.5.6, 1.6.2 |
| Fix Version/s: | 1.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Leonardo Diez | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 5.5 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
Working with 1.5.6 version and after a data import and some data manipulation on a 40 million collection, the database its corrupt. It seems that the data can be accessed normally, but when trying to run some data processing using a java process, an error occurs and ask for a database repair. |
| Comments |
| Comment by Dwight Merriman [ 25/Nov/10 ] |
|
i have made a new generalized ticket for clarity |
| Comment by Leonardo Diez [ 08/Sep/10 ] |
|
I've solved the problem temporary changing the limit to 4M to run the repair process, because I know all my string data doesn't reach that size. Maybe there is a good idea to use a SIGSEV handler to avoid segmentation fault during data validation. |
| Comment by Leonardo Diez [ 08/Sep/10 ] |
|
I've applied your changes to 1.6.2 code, compiled it and tried to execute a db reparation again. The problem keeps there. The backtrace line changes to: /opt/mongo/bin/mongod(_ZNK5mongo11BSONElement8validateEv+0x6d). |
| Comment by auto [ 03/Sep/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: try to prevent segfault on corrupt data |