Error Message

When mounting the file system in the DR environment, it fails with below error:

# mount  -t vxfs  /dev/vx/dsk/testdg/vol1 /mnt

log replay in progress

UX:vxfs fsck: ERROR: V-3-20749: file system does not contain a valid log

UX:vxfs fsck: ERROR: V-3-20700: cannot perform log replay

file system is not clean, full fsck required

full file system check required, exiting ...

UX:vxfs mount.vxfs: ERROR: V-3-26883: fsck log replay exits with 12

UX:vxfs mount.vxfs: ERROR: V-3-26881: Cannot be mounted until it has been cleaned by fsck. Please run "fsck -t vxfs -y /dev/vx/rdsk/9013_ROAMINGSPONSRDBLOGDG/origlogB" before mounting

A file system is simply a method for storing and organizing computer files and the data they contain to make it easy to find and access them. More formally, a file system is a set of abstract data types (such as metadata) that are implemented for the storage, hierarchical organization, manipulation, navigation, access, and retrieval of data.
 

The disk layout is the way file system information is stored on disk.

The log_version is related to transaction logging. When new transaction types are included in a VxFS product release, the version number is incremented.

A lower VxFS product version won't be able to understand newly added transaction types included in a higher VxFS product version.

 

The target (remote) system should be running the same version or higher than production.


Hardware replication environments, such as EMC SRDF, Hitachi TrueCopy are common environments where this issue could be encountered.

On Veritas File System (VxFS), several disk layout versions and log_versions are supported to provide new feature support.

The log_version is also increased depending on the VxFS product version:

infoScale Version         Supported log_versions 

7.1                                9,10,11 & 12

7.2                                9,10,11,12 & 13

7.3.1                             9,10,11,12 & 13

P.S: log_version 11 is supported from InfoScale 7.1 onwards. Log_version 13 is not supported with InfoScale 7.1 or lower

The file system has been updated resulting in an update of the log version to 13 with VRTSvxfs 7.3.1 on the production host.
 

The file system is then being replicated to the DR server with the 7.1 Veritas stack (where logversion 12 is the highest supported version) .

About file system disk layouts

https://docs.infoscale.com/ 

 

The above mount error is occurring for all mount points due to log version mismatch.

The fsck utility performs a log version validation. which is failing here, hence the standard fsck check fails.

NOTE: If the 7.3.1 fsck binary is used, no fsck errors or inconsistency is detected or reported

Reproduction steps:

1.Install VXFS7.3.1 and create a VXFS filesystem as follows :

  # mkfs -t vxfs -o version=10 /dev/vx/rdsk//  

2.Uninstall 7.3.1 & install VXFS 7.1 version

3.Try mounting the file system, it fails with following messages

# mount  -t vxfs  /dev/vx/dsk/testdg/vol1 /mnt

log replay in progress

UX:vxfs fsck: ERROR: V-3-20749: file system does not contain a valid log

UX:vxfs fsck: ERROR: V-3-20700: cannot perform log replay

file system is not clean, full fsck required

full file system check required, exiting ...

UX:vxfs mount.vxfs: ERROR: V-3-26883: fsck log replay exits with 12

UX:vxfs mount.vxfs: ERROR: V-3-26881: Cannot be mounted until it has been cleaned by fsck. Please run "fsck -t vxfs -y /dev/vx/rdsk/testdg/vol1" before mounting

But If we check the flags set on FS through fsdb, FULLFSCK flag is not set.

> 8192B.p S

super-block at 00000008.0000

magic a501fcf5  version 10

uuid 0554a25b-389a-0800-c52c-0000649df307

free 10464674  ifree 0

efree  0 1 2 1 3 1 1 0 1 0 1 1 0 1 0 1 1 1 1 1 1 2 1 0 0 0 0 0 0 0 0 0

flags 4000       <<< FULLFSCK = 0x0001 (not set)

The solution is to upgrade the DR host to the same version as the production host.

If the file system disk layout or VxFS log version is updated on the production host first, and the DR server is running a lower Veritas product version, a full fsck may be required to mount the file system in the DR environment.

ETrack: 3958502