[SERVER-7137] Put more debugging information when magic number does not match in the extents Created: 24/Sep/12  Updated: 06/Dec/22  Resolved: 03/Oct/16

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: 2.0.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Randolph Tan 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

Issue Links:
Related
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

Whenever we get an assertion about this, we currently have little clue what is wrong other than it does not match. It would probably be more helpful if we dump the contents of the extent (length, myLoc, xnext, xprev, magic) as well as the next and previous extents.



 Comments   
Comment by Ian Whalen (Inactive) [ 03/Oct/16 ]

Someone can/should reopen if they think we're seeing this more and it justifies reconsidering.

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