Issues Fixed in Lightbits 3.18.4
ID | Description |
|---|---|
48532 | node-manager can fail to start if the number of drives present falls below the minimum required for that node's configured layout. For example - after a drive failure, power loss, or planned maintenance. In earlier releases, the node would start with the missing drive marked as failed; affected releases instead fail to start entirely. Workaround: set |
48041 | Lightbits management uses state machines that retry operations with an increasing backoff delay until they succeed, to absorb lengthy or racy operations. After a long enough run of consecutive failures of the same operation, the backoff stopped increasing and collapsed to effectively no delay: this was after roughly 1.5 minutes of consecutive retries in the 3.18.x release family, and roughly 16 hours in the 3.19.x and 3.20.x families. The resulting continuous retries could highly load a CPU core and emit a large number of log messages, potentially discarding older diagnostic history needed to investigate the original failure on that node. |
48012 | A stale volume or snapshot could remain on a server and block deletion of the snapshot that it was cloned from. This can happen when a volume or snapshot is created while a server's node-manager service is down (either the service alone, or the whole server powered off), and is deleted exactly as the node-manager is recovering. It applies to the following: a volume that has no snapshots created from it. and a snapshot whose source volume no longer exists and that has no other snapshots created from that volume. If the stale object is a clone - or a snapshot of a clone - deletion of the snapshot it was originally created from never completes. That snapshot stays in Deleting state, also blocking any future operations on the source volume. For example: volume V0 has snapshot S0, and clone C1 is created from S0. If C1 becomes stale, deleting S0 never completes - S0 stays in Deleting state - and no new operation on V0 can start. A stale volume or snapshot could also prevent a rebuild from completing for these volumes/snapshots. Data is not lost, and affected volumes remain accessible and continue to serve I/O. Workaround: Contact Lightbits Support to manually remove the stale volume or snapshot. |
© 2026 Lightbits Labs™