Issues Fixed in Lightbits 3.10.1

ID	Description
37831	In some cases, silent data corruption on an SSD could cause a node crash instead of attempting to recover the data and reporting an event. This can occur if the SSD returns invalid data rather than an I/O error.
37395	In some rare racy conditions a server may remain stuck in a deleting state.
34169	Duroslight crashes (segfault) during startup on Sapphire Rapids, when the kernel is in lockdown mode.
33998	A node could fail on GFTL assertion objects_info_digest != write_unit_md_objects_info_digest under the following conditions: At some earlier point in time, GFTL abrupt recovery occurred. Before this recovery, a snapshot was deleted, while more recent snapshots of the same volume and/or clones from this snapshot are present. Note that when using K8s or OpenStack orchestration, Lightbits CSI/Cinder drivers could create and delete snapshots as part of cloning a volume.
17329	Lightbits exposes latency information per request size. The time window for latency measurement is not synchronized with the measurement of nr read/write requests. Therefore a weighted average calculation of latency over all request sizes will result in inaccurate latency information.

Last updated on

Was this page helpful?