DR in maintenance mode after reaching container limit (4039149)

After reaching the maximum container limit, (32, 64, or 128 depending on DR model), the DR goes into maintenance mode with the following reason as shown in output from "system --show":

System State                    : Maintenance Mode
Reason                          : Installing container "testtest-127"

ocafsd.log entries below:

2017-10-06 12:28:08 ocafsd[73619]: [74244] NOTICE: Node is read-only
2017-10-06 12:28:08 ocafsd[73619]: [74244] NOTICE: Initializing mtab for
container testtest-127, config testtest-127-1-132 tgtdir (null) at
/containers/testtest-127 (Node: 1 ID: 132).
2017-10-06 12:28:08 ocafsd[73619]: [74244] NOTICE: Alloc MTAB 0x7f573f184000
2017-10-06 12:28:08 ocafsd[73619]: [74244] NOTICE: starting optimizer with mtab
0x7f573f184000
2017-10-06 12:28:08 ocafsd[73619]: [74244] NOTICE: dedupe_start: mtab: 132
group: 0
2017-10-06 12:28:08 ocafsd[73619]: [74244] NOTICE: Dedupe initialized on
container testtest-127
2017-10-06 12:28:08 ocafsd[73619]: [74244] ERROR: Failed to start o3e stats (No
space left on device)
2017-10-06 12:28:08 ocafsd[73619]: [74244] ERROR: Unable to start optimizer (No
space left on device)

To be fixed in a future DR software release.

Please open a Support service request for immediate assistance.