> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/releases/2026/v8.6.10/fixes.md).

# Fixes

Generally available since February 3, 2026. Review the critical, highly recommended, and recommended fixes included in Silk v8.6.10.

## Critical Fixes

Fixes for issues that could significantly affect system availability, data security, or the ability to perform essential operations. Prioritize applying these fixes.

<table><thead><tr><th width="116.2962646484375">Fix ID</th><th>Description</th></tr></thead><tbody><tr><td>144135</td><td>Improved m.node live migration reliability to prevent system stalls in scenarios involving recent c.node scale-in operations.<br><br>Live migrations can now proceed safely after c.node scale-ins without triggering system recovery conditions, reducing the risk of disruption during maintenance operations.</td></tr><tr><td>143313</td><td>Improved handling of split-brain scenarios where the system could stall instead of performing recovery or takeover. Fencing behavior now exits cleanly without impacting other c.nodes.</td></tr><tr><td>132174</td><td>Resolved an issue where a failure during c.node phase-in could cause a system stall, improving overall system reliability.</td></tr></tbody></table>

## Highly Recommended Fixes

Fixes for significant functional or operational issues that aren’t expected to affect overall system availability or security. Applying these fixes is strongly recommended to maintain reliable operation and avoid potentially disruptive behavior.

<table><thead><tr><th width="118.5185546875">Fix ID</th><th>Description</th></tr></thead><tbody><tr><td>142816</td><td>Enhanced d.node recovery handling to prevent degraded system states caused by invalid recovery paths.</td></tr><tr><td>142618</td><td>Optimized c.node memory allocation to reduce inefficiencies and prevent unnecessary c.node recovery.</td></tr><tr><td>142223</td><td>Resolved an issue where replication bandwidth metrics could display incorrectly following certain failover scenarios, while replication continued to operate as expected.</td></tr><tr><td>140341</td><td>Improved c.node failback handling during I/O bring-up to avoid stall conditions during scale-out failures.</td></tr><tr><td>138144</td><td>Resolved an issue where logs were not received as expected. The system now reliably receives and processes logs, ensuring better visibility into system activity.</td></tr><tr><td>138102</td><td>Resolved an issue affecting controlled system startup behavior. Enhanced startup handling ensures the system initializes in a controlled and predictable way.</td></tr><tr><td>136364</td><td>Fixed an issue where a node redeploy that did not complete successfully could leave the node in an error state and trigger repeated installation attempts.<br><br>Enhanced handling of incomplete redeploys ensures nodes recover cleanly from error states, preventing repeated installation attempts and improving overall system stability.</td></tr><tr><td>132321</td><td>Addressed a race condition between volume unmap operations and I/O that could trigger unnecessary c.node recovery.</td></tr><tr><td>129991</td><td>Addressed a race condition between volume unmap operations and I/O that could trigger unnecessary c.node recovery.</td></tr><tr><td>123663</td><td>Eliminated a race condition during LU removal between global and local hash tables that could lead to unnecessary c.node recovery.</td></tr></tbody></table>

## Recommended Fixes

Fixes for smaller or more limited issues that may affect specific workflows, behaviors, or user experiences. These fixes are recommended for customers who use the affected functionality.

<table><thead><tr><th width="117.03704833984375">Fix ID</th><th>Description</th></tr></thead><tbody><tr><td>141602</td><td>Enhanced API error handling ensures more consistent and predictable behavior.</td></tr><tr><td>141502</td><td>Resolved an issue where Flex logs were not consistently collected during remote operations.</td></tr><tr><td>137642</td><td>Corrected an issue where physical capacity values shown in the SDP Management Console and Clarity reports could appear significantly lower than the sum of all DataPod volumes. Capacity reporting is now accurate and consistent across dashboards and reports.</td></tr><tr><td>134932</td><td>Improved stability for Linux hosts with high session counts, resolving an issue that lead to temporary host disconnects during volume discovery operations.</td></tr><tr><td>141643<br>135541</td><td>Resolved an issue where physical and allocated capacity values could be inconsistent in Clarity reports, causing mismatches between per-volume totals and overall DataPod capacity usage.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.silk.us/releases/2026/v8.6.10/fixes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
