# vxvol -f -g raidgroup -o delayrecover start raidvol
VxVM vxvol ERROR V-5-1-10128 Unexpected kernel error in configuration update
A vxconfigd log with debug enabled captured at the time of running the start / recover command may show the following entries:
01/06 12:53:57: VxVM vxconfigd DEBUG V-5-1-681 IOCTL KTRANS_COMMIT: failed: errno=22 (Invalid argument)
01/06 12:53:57: VxVM vxconfigd DEBUG V-5-1-681 IOCTL GET_KTRANS_STATE: return 0(0x0)
Results: dgiid=1024.51 pendtid=0.68180 conftid=0.68178 state=ABORTED
abort_err=1
01/06 12:53:57: VxVM vxconfigd DEBUG V-5-1-681 IOCTL KTRANS_ABORT: failed: errno=22 (Invalid argument)
01/06 12:53:57: VxVM vxconfigd DEBUG V-5-1-681 IOCTL SET_KMEM id=0 size=84: return 0(0x0)
01/06 12:53:57: VxVM vxconfigd DEBUG V-5-1-5892 REQUEST FAILURE: client 1993019980: Unexpected kernel error in configuration update
01/06 12:53:57: VxVM vxconfigd DEBUG V-5-1-681 IOCTL KTRANS_ABORT: failed: errno=22 (Invalid argument)
01/06 12:53:57: VxVM vxconfigd DEBUG V-5-1-681 IOCTL SET_KMEM id=0 size=84: return 0(0x0)
01/06 12:53:57: VxVM vxconfigd DEBUG V-5-1-5331 ddb_trans_abort()
VxVM uses an integer variable to store the starting block offset of a sub-disk in a RAID5 column.
This variable overflows when a sub-disk is located at an offset greater than 2147483647 blocks (1TB) and results in a failure to start the volume.
This issue is tracked via incident e2657797.
VxVM code is now modified to handle integer overflow conditions for RAID5 volumes.
This issue is fixed in the VxVM 5.1SP1RP2P2HF9 hotfix for Linux platform.
This hotfix requires the 5.1SP1RP2P2 patch to be installed on the system, which can be downloaded from: https://sort.Veritas.com/patch/searchmatrix/22/3/4
Please contact Veritas Technical support to obtain the hotfix for this issue.
Applies To
This issue applies to all 5.x Veritas Volume Manager (VxVM) releases.