st_device_enlarge can corrupt EXAStorage metadata and later cause data corruption in a limited storage area
Details
| Detail name | Value |
|---|---|
| Changelog Number | 31028 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.29.0, Exasol 2025.1.0, Exasol 2026.1.0 |
| Fix Versions | Exasol 2026.1.1, Exasol 2025.1.12 |
| Resolution Date | 2026-07-02 |
Description
In Exasol 8, increasing an EXAStorage device with the ConfD job st_device_enlarge can lead to storage metadata corruption. As a result, this can cause data corruption in a limited storage area once the data volume is enlarged automatically to use the newly-available space. Symptoms of this problem may include:
- Unexpected database restarts when querying certain data
- Unexpected backup failures due to checksum errors
Note: The problem may not appear immediately after st_device_enlarge was used. It can remain unnoticed until the affected storage area is used later.
Workaround
Do not use st_device_enlarge until you update to one of the fix versions. If the problem has already occurred, or you have used st_device_enlarge in the past, contact Exasol Support immediately to check if you are affected and for recovery options. In most cases, the data will need to be restored from the last available remote backup, therefore we recommend to remove the expiration dates from your latest remote backup.
Fix
The storage metadata is now updated correctly when st_device_enlarge is used.
