# Corrupted WAL table & data due to a previous full disk or kernel limits error

**URL:** <https://community.questdb.com/t/corrupted-wal-table-data-due-to-a-previous-full-disk-or-kernel-limits-error/150>\
**Category:** Community\
**Tags:** question\
**Created:** [August 15, 2024, 6:23pm UTC](https://community.questdb.com/t/corrupted-wal-table-data-due-to-a-previous-full-disk-or-kernel-limits-error/150 "2024-08-15T18:23:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex004/uploads/questdb/original/1X/b6b1b349e598d0550947e63d7923a9d7df0279eb.png) [@system](https://community.questdb.com/u/system)\
**Post date:** [August 15, 2024, 6:23pm UTC](https://community.questdb.com/t/corrupted-wal-table-data-due-to-a-previous-full-disk-or-kernel-limits-error/150/1 "2024-08-15T18:23:59Z")

</div>

What do I do? The table is corrupted.

---

<div class="post-metadata">

**Author:** ![puzpuzpuz](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/puzpuzpuz/32/25_2.png) [@puzpuzpuz](https://community.questdb.com/u/puzpuzpuz)\
**Post date:** [August 15, 2024, 6:24pm UTC](https://community.questdb.com/t/corrupted-wal-table-data-due-to-a-previous-full-disk-or-kernel-limits-error/150/2 "2024-08-15T18:24:15Z")

</div>

You need to skip the problematic transation using the [RESUME WAL](https://questdb.io/docs/reference/sql/alter-table-resume-wal/) SQL statement.

If there are multiple transactions that rely the WAL data which is now corrupted, follow this guidance:

> **[ALTER TABLE RESUME WAL | QuestDB](https://questdb.io/docs/reference/sql/alter-table-resume-wal/#diagnosing-corrupted-wal-transactions)**
>
> ALTER TABLE RESUME WAL SQL keyword reference documentation.