[SERVER-5489] Mongod crash Created: 03/Apr/12 Updated: 15/Aug/12 Resolved: 19/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Internal Code, Stability |
| Affects Version/s: | 2.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
Getting repeatable crashes after inserting documents from a find().snapshot() then calling ensureIndex on the _id field (that should already exist?) |
| Comments |
| Comment by Tad Marshall [ 25/Jun/12 ] | |||||||||||||||||||||||||||
|
Setting Backport to No because there is no code change associated with this ticket. | |||||||||||||||||||||||||||
| Comment by Andy Schwerin [ 19/May/12 ] | |||||||||||||||||||||||||||
|
Appears to be data corruption unrelated to mongo operation. | |||||||||||||||||||||||||||
| Comment by Daniel Gottlieb (Inactive) [ 19/May/12 ] | |||||||||||||||||||||||||||
|
Nope. I was just creating a case in the event the error message/data was at all meaningful. Seems this failure is pretty generic and merely indicates that somewhere data got corrupted. Feel free to resolve/close as protocol dictates. | |||||||||||||||||||||||||||
| Comment by Andy Schwerin [ 18/May/12 ] | |||||||||||||||||||||||||||
|
This still burning you? | |||||||||||||||||||||||||||
| Comment by Daniel Gottlieb (Inactive) [ 20/Apr/12 ] | |||||||||||||||||||||||||||
|
From your comment it seems pretty likely the error is that the data files are corrupt. I don't think there's any real trails that might help explain how it got to there (whether or not it was human error). A further mention, my version of mongod: db version v2.1.0, pdfile version 4.5 won't even start up as it fails to read the .ns file (and throws the same assert as above as far as I can tell). Whichever version of mongod Jeff is running seems to care less about the broken .ns file (from what I remember, it only complains about a problem when doing a find on the system.indexes collection for him). | |||||||||||||||||||||||||||
| Comment by Daniel Gottlieb (Inactive) [ 20/Apr/12 ] | |||||||||||||||||||||||||||
|
This is a tar of mongod database files. Just untar them and start a mongod with --dbpath pointing to this directory. | |||||||||||||||||||||||||||
| Comment by Andy Schwerin [ 18/Apr/12 ] | |||||||||||||||||||||||||||
|
Yeah, this particular assertion indicates that some region of memory that we believe is a database file doesn't have the expected magic number at the front. Could mean wild pointer, could mean corrupt file | |||||||||||||||||||||||||||
| Comment by Daniel Gottlieb (Inactive) [ 18/Apr/12 ] | |||||||||||||||||||||||||||
|
Damn, last time the log/stack trace seemed to be enough! I'll see if I can find a dataset for reproduction. | |||||||||||||||||||||||||||
| Comment by Andy Schwerin [ 18/Apr/12 ] | |||||||||||||||||||||||||||
|
Apparently relevant section of log file:
| |||||||||||||||||||||||||||
| Comment by Andy Schwerin [ 18/Apr/12 ] | |||||||||||||||||||||||||||
|
Dan, Do you have a set of (ideally simple) repro instructions? Preferably of the form "run attached script," but anything you can give us. There's not much context in this bug report, right now. |