Huge resize operations on archive volumes can lead to their corruption

Detail name	Value
Changelog Number	5820
Type	Bug
Status	Open
Affected Versions

Problem

Huge resize operations on large archive volumes can take a lot of time. This can lead to an internal timeout (~ 5 min) and thus to an automatic rollback of the resize operation. Due to a bug in this mechanism the triggered rollback can lead to a corruption of the archive volume.

Workaround

Split the huge resize operation into smaller parts and repeat the smaller operation as many times as needed. The biggest recommended resize step is 1 TiB.

Repairing a broken archive volume

Attention: Contents of affected archive volumes is lost and can not be restored.
However, to get back into an operational state, Exasol support will be able to manually re-format such a broken volume.