Unable to force start VxVM volume due to stale snap objects - VxVM vxvol ERROR V-5-1-10128 Unexpected kernel error in configuration update
Article ID: 100019921
Updated On:
Description
Error Message
# vxvol -g testdg1 -f start testvol1VxVM vxvol ERROR V-5-1-10128 Unexpected kernel error in configuration update
Resolution
VxVM Volume is shown in a "DISABLED ACTIVE" state.
# vxprint -qhtg testdg1
v testvol1 - DISABLED ACTIVE 14030000000 SELECT - fsgenpl testvol1-01 testvol1 DISABLED ACTIVE 14030000256 STRIPE 3/128 RWsd testdg101-01 testvol1-01 testdg101 0 4676666752 0/0 sdb ENAsd testdg102-01 testvol1-01 testdg102 0 4676666752 1/0 sdc ENAsd testdg103-01 testvol1-01 testdg103 0 4676666752 2/0 sdd ENAdc testvol1_dco testvol1 testvol1_dclv testvol1_dcl - ENABLED ACTIVE 964912 SELECT - genpl testvol1_dcl-01 testvol1_dcl ENABLED ACTIVE 964912 CONCAT - RWsd testdg101-02 testvol1_dcl-01 testdg101 4676666752 964912 0 sdb ENApl testvol1_dcl-02 testvol1_dcl ENABLED ACTIVE 964912 CONCAT - RWsd testdg102-02 testvol1_dcl-02 testdg102 4676666752 964912 0 sdc ENA
When trying to force start the data volume, it reports the following error message:
# vxvol -g testdg1 -f start testvol1
VxVM vxvol ERROR V-5-1-10128 Unexpected kernel error in configuration update
The error is seen due to stale snap objects associated with the volume.
STEPS:
Remove (unprepare) the stale snap objects.
# vxsnap -g testdg1 print testvol1
# vxsnap -g testdg1 -f unprepare testvol1
After removing the stale snap objects associated the volume, the volume can now be started and the file system mounted.
# vxvol -fg testdg1 start testvol1
The snap objects can be recreated by running:
# vxsnap -g testdg1 prepare testvol1
Issue/Introduction
When trying to start a disabled Veritas Volume Manager (VxVM) volume, it even fails to start when force (-f) starting with vxvol.
Was this article helpful?
Yes
No
Powered by
