ERROR V-5-1-10128 Configuration daemon error 441

Article: 100021542
Last Published: 2022-02-01
Ratings: 0 0
Product(s): InfoScale & Storage Foundation

Problem

ERROR V-5-1-10128 Configuration daemon error 441

 

Solution

This error can occur when performing various operations.  Two are discussed here. 
 
1. Attempting to stop a volume, both by using the vxvol command and by offlining the VCS service group/resource (Mountresource)
 
VxVMvxvol ERROR V-5-1-10128 Configuration daemon error 441
 
2. Attempting to upgrade disk group version
 
bash-3.00#vxdg upgrade snfs04a
VxVMvxdg ERROR V-5-1-2356 Disk group snfs04a: upgrade failed: Configuration daemonerror 441
 
Viewing the private region in the first example stopping volume) shows:
 
#vxprivutil dumpconfig <priv_path> |vxprint -D - -ht
<snip>
vvxatvol - DISABLED CLEAN 2027008 SELECT- fsgen
plvxatvol-01 vxatvol DISABLED CLEAN 2027008 CONCAT- RW
sdvxatdg01-01 vxatvol-01 vxatdg01 0 2027008 0- DIS
 
This information does not match the current status.  Assuming the volume is operational vxprint shows:
 
vvxatvol - ENABLED ACTIVE 2027008 SELECT- fsgen
plvxatvol-01 vxatvol ENABLED ACTIVE 2027008 CONCAT- RW
sdvxatdg01-01 vxatvol-01 vxatdg01 0 2027008 0- ENA
 
Information contained in the private region (Volume Manager header) held in kernel memory is different than the private region on the disk(s) of the diskgroup.
 
Two different solutions are provided.
 
vxdgflush <diskgroup_name>
 
If successful, this command writes the kernel memory to the hard disk(s) to avoid unmounting the volumes and deporting the diskgroup.  Otherwise, unmount all volumes in the affected diskgroups and deport and reimport it.
 
vxdg deport <diskgroup_name>
vxdg import <diskgroup_name>
 
This condition can presumably occur in any version of Volume Manager in any supported Operating System.
 

 

Was this content helpful?