FVS Storage incident notice

Impact

Applications launched with cpak v2.1.x could take several seconds to appear. The delay was most visible on the first launch and affected browsers, communication clients, development tools and other desktop applications. Applications that had already started continued to run normally.

Cause

FVS Storage preparation was running as part of every application launch. Systems with a cold cache or several package layers paid that cost before the application process could start. No package or user data was corrupted.

Resolution

cpak v2.2.0 moves storage preparation outside the normal launch path and reuses a prepared filesystem view. Existing stores are updated in place, with visible progress when a migration is required. The operation can resume after an interruption.

The resolution announcement describes the update and the information needed for any remaining startup report.