Issues Fixed in Lightbits 3.4.1
| ID | Description |
|---|---|
| 28728 | DCPMM devices might not be identified by profile-generator after power-up, leading to a non-optimized profile after a Lightbits upgrade of systems with DCPMM DIMMs installed. |
| 28314 | The backup footer file sometimes contains an incorrect size, and should not be used to determine the restored volume size. The original volume size for the restore command can be found in the backup header file. This issue was fixed in release 3.4.1, where the restore command "size" is optional, and the Lambda will read the correct volume size. |
| 27046 | Lightbits events (lbcli list events) are capped at 64K events. For systems that have had more than 64k events, new events will be pushed to the end of the events list and may even be lost. Each event has a unique ID that is an incremental counter, This counter wraps around after 64K events. Events are sorted from the last event (largest ID) to the oldest. When there are more than 64K events, the ID wraps around and pushes the newest events to the end of the queue. The events cleaner mechanism (maximum events stored is 10k events) will at some point begin and remove events that are incorrectly assumed to be oldest. |
| 15880 | The core configuration for Samsung SSDs requires a manual override. The number of cores allocated for the GFTL reader should be limited to four cores. |
| 10346 | Many SSD removals during SSD resets can lead to a memory leak and require a server reboot. |