CONTAP-480647: Critical WAFL Inconsistency triggered by Pseudo Bad Block Corruption
Issue
- WAFL inconsistency is reported on a volume and the following alerts are seen in the event logs:
[Node-01: wafl_exempt04: wafl.raid.incons.userdata:error]: WAFL inconsistent: inconsistent user data block at VBN 1234567890 (vvbn:12345670 fbn:0 level:0) in public inode (fileid:222222 snapid:111 file_type:1 disk_flags:0x8002 error:121 raid_set:1) in volume vol_1@vserver:9b3XXXX-97XX-11XX-a2XX-000dXXXXXXXa.
[Node-01: wafl_exempt04: wafl.incons.userdata.vol:alert]: WAFL inconsistent: volume vol_1@vserver:9b3XXXX-97XX-11XX-a2XX-000dXXXXXXXa has an inconsistent user data block. Note: Any new Snapshot copies might contain this inconsistency.
[Node-01: wafl_exempt04: callhome.wafl.inconsistent.user.block:alert]: Call home for WAFL INCONSISTENT USER BLOCK
- WAFL is unable to recover the blocks that are marked as a pseudo bad block (E_PSEUDOBAD_BLOCK). Consequently, WAFL flags the file system as inconsistent to prevent further data corruption.
- The corruption is localized to the reported volume, with no signs of RAID or aggregate-level errors. This indicates that the issue is confined to the specific volume and does not affect at broader level.