[SERVER-43991] encountered an illegal file format or internal value: 0x0: Created: 14/Oct/19 Updated: 27/Oct/23 Resolved: 08/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.0.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | krzysztof osmulski | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Sprint: | Storage Engines 2019-11-04 |
| Participants: | |
| Story Points: | 3 |
| Description |
|
server did not crash not restart. actual up time is 45 days. Mongo process did not restart from that time got crash:
|
| Comments |
| Comment by Brian Lane [ 08/Dec/19 ] |
|
Thanks clydzik@wp.pl, Feel free to reopen or create a new issue if you experience any other issues. -Brian |
| Comment by krzysztof osmulski [ 07/Dec/19 ] |
|
I can confirm that there is a problem with cheap ssd. |
| Comment by Danny Hatcher (Inactive) [ 06/Dec/19 ] |
|
Have you experienced issues even after switching disks? |
| Comment by Danny Hatcher (Inactive) [ 29/Oct/19 ] |
|
At this point in time we do believe the issue has to do with data corruption at the disk level. I believe the best path forward is to try another disk. If you still experience issues on a new disk, we can look further. This case is a good example of the value of Replication. If you have three different servers containing copies of your data, one disk failing is not a problem as you still have two copies of your data you can sync from. |
| Comment by krzysztof osmulski [ 26/Oct/19 ] |
|
This is just one server standalone installation. But since I experienced more issues I can believe this may be a storage issue what is difficult to confirm. Now I would like to verify storage sector by sector but not sure what would it be for Linux ext4. I also did small tweaks on journalling in mongo and FS as guided for SSD drive. |
| Comment by Danny Hatcher (Inactive) [ 25/Oct/19 ] |
|
clydzik@wp.pl, we are still investigating this problem but we believe this issue may have been caused by disk corruption. Did the server in question experience any other issues around the time of the assertion? Have you seen the issue on other servers or just one? |
| Comment by krzysztof osmulski [ 14/Oct/19 ] |
|
during mongod --verify found such log: 2019-10-14T20:27:08.648+0200 I STORAGE [initandlisten] Invalid BSON detected at RecordId(36455202): InvalidBSON: not null terminated string in element with field name 'url' in object with _id: "7870558706". Deleting.
not sure if this is related |