[SERVER-4864] certain new extent sizes may crash the server Created: 03/Feb/12  Updated: 11/Jul/16  Resolved: 10/Feb/12

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.0.2
Fix Version/s: 2.1.1

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

32bit


Operating System: ALL
Participants:

 Description   

If you attempt to set an oplog size of 512mb on a 32-bit system, the database will abort with an assert.
This is due to the extent splitter code not using the same max-extent value that the extent creation code is using.
Since it seems unlikely to create an extent size that fits between the two sizes, this bug doesn't affect many users. Note that the max extent size is affected by --smallfiles (and, by extension, 32-bit platforms).



 Comments   
Comment by auto [ 09/Feb/12 ]

Author:

{u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-4864 avoid creating invalid extent sizes
Branch: master
https://github.com/mongodb/mongo/commit/c1a2188dfb122c34baece5275b6fa1d446a86319

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