After P2V Conversion using vCenter standalone converter 6.6, OS level file system reported to be corrupt on RHEL 7.9 VM

Products

• VMware vCenter Server

Issue/Introduction

After performing P2V conversion using vCenter standalone converter for RHEL 7.9 VMs, you might notice a file system corruption within OS. 

 

Environment

vCenter Converter standalone 6.6

Cause

As per the OS vendor, they have noticed a newer version of e2fsprogs working in multiple destination virtual machine file systems post conversion, which is not supported on RHEL 7.9.

> grep -i fsck /var/log/messages
Dec  3 17:54:21 VM_Name kernel: EXT4-fs (dm-2): error count since last fsck: 26015
Dec  3 17:54:21 VM_Name kernel: EXT4-fs (dm-1): error count since last fsck: 1
Dec  4 17:56:09 VM_Name kernel: EXT4-fs (dm-2): error count since last fsck: 26907
Dec  4 17:56:09 VM_Name kernel: EXT4-fs (dm-1): error count since last fsck: 1

 

> dmesg  | grep -i ext | tail
[2231087.626037] EXT4-fs error (device dm-2): ext4_xattr_block_get:321: inode #1048774: comm systemd-journal: bad block 4198466
[2231087.628514] EXT4-fs error (device dm-2): ext4_xattr_block_get:321: inode #1048775: comm systemd-journal: bad block 4198467
[2231149.722386] EXT4-fs error (device dm-2): ext4_xattr_block_get:321: inode #1048774: comm systemd-journal: bad block 4198466
[2231149.724924] EXT4-fs error (device dm-2): ext4_xattr_block_get:321: inode #1048775: comm systemd-journal: bad block 4198467
[2231251.573964] EXT4-fs error (device dm-2): ext4_xattr_block_get:321: inode #1048774: comm systemd-journal: bad block 4198466
[2231251.576333] EXT4-fs error (device dm-2): ext4_xattr_block_get:321: inode #1048775: comm systemd-journal: bad block 4198467
[2231281.816258] EXT4-fs error (device dm-2): ext4_xattr_block_get:321: inode #1048774: comm systemd-journal: bad block 4198466
[2231281.818038] EXT4-fs error (device dm-2): ext4_xattr_block_get:321: inode #1048775: comm systemd-journal: bad block 4198467
[2231338.473608] EXT4-fs error (device dm-2): ext4_xattr_block_get:321: inode #1048774: comm systemd-journal: bad block 4198466
[2231338.475611] EXT4-fs error (device dm-2): ext4_xattr_block_get:321: inode #1048775: comm systemd-journal: bad block 4198467

> grep -i fsck /var/log/messages
Dec  5 12:08:18 VM_Name systemd-fsck: /dev/mapper/root_vg-root has unsupported feature(s): metadata_csum
Dec  5 12:08:18 VM_Name systemd-fsck: e2fsck: Get a newer version of e2fsck!
Dec  5 12:08:18 VM_Name systemd-fsck: fsck failed with error code 8.
Dec  5 12:08:18 VM_Name systemd-fsck: Ignoring error.
Dec  5 12:08:19 VM_Name kernel: EXT4-fs (dm-1): warning: mounting fs with errors, running e2fsck is recommended
Dec  5 12:08:19 VM_Name systemd-fsck: /dev/sda1 has unsupported feature(s): metadata_csum
Dec  5 12:08:19 VM_Name systemd-fsck: e2fsck: Get a newer version of e2fsck!
Dec  5 12:08:19 VM_Name systemd-fsck: fsck failed with error code 8.
Dec  5 12:08:19 VM_Name systemd-fsck: Ignoring error.
Dec  5 12:08:20 VM_Name systemd-fsck: /dev/mapper/root_vg-var--tmp has unsupported feature(s): metadata_csum
Dec  5 12:08:20 VM_Name systemd-fsck: fsck failed with error code 8.
Dec  5 12:08:20 VM_Name systemd-fsck: e2fsck: Get a newer version of e2fsck!

Resolution

The fix will be available in the upcoming version of VCenter Converter standalone.

Currently, the RHEL OS support team is able to fix the file system corruption and bad sectors on the operating system side.