VxFS Filesystem header corruption seen post upgrading from Infoscale 7.4.2 to 8.x

Article: 100074723
Last Published: 2025-08-13
Ratings: 0 0
Product(s): InfoScale & Storage Foundation

Problem

After upgrading from InfoScale 7.4.2 to 8.x, the Veritas File System (VxFS) fails to mount and reports a Filesystem header corruption.

Error Message

Mount Fails with the error below

UX:vxfs fsck: ERROR: V-3-20448: No valid fset headers found
UX:vxfs fsck: ERROR: V-3-20694: cannot initialize aggregate

When using fsdb to check the metasave, it shows the following error:

$ echo "8192B.p S" | sudo fsdb -F vxfs /dev/vx/rdsk/<DG>/<VOL>
fileset header checksum error

Cause

VxFS introduced new fset header filed (fsh_rtime) in DLV 17 after VxFS 8.0. While upgrading from 7.4.2 to 8.x, if the file system isn't unmounted cleanly, log replay is required to replay those transactions that haven't been flushed to disk.

During log replay, when calculating the size of file system log entries, the new file set header is used unexpectedly when replaying an fset header transaction. Since the size of new fset headers increased due to the addition of fsh_time filed, replay of such fset header transaction could overwrite the adjacent transactions, hence the corruption.

Solution

A hotfix is now available for this issue in the current version(s) of the product(s) mentioned. Please contact  Technical Support to obtain this fix. This hotfix has not yet gone through any extensive Q&A testing. Please note that we as a company reserve the right to remove any fix from the targeted release if it does not pass quality assurance tests. Our plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

 

References

JIRA : STESC-9637 Etrack : 4175191

Was this content helpful?