There are situations when a hardware failure will cause a Veritas Volume Manager volume where logging is utilized to set its 'badlog' flag to 'on'. Even after the hardware is repaired and the associated log is re-created this 'badlog=on' will persist. This condition will prevent the volume log from functioning correctly.

To reset the configuration flag from 'badlog=on' to 'badlog=off' perform. the following procedure.

1. Preserve a vxprint -ht and a vxdisk -o alldgs list.

2. Preserve the following for each volume to be reset:

# vxprint -g rootdg -rhmvps > .config

3. Umount the VXFS file system and delete the volume to be re-created.

# umount /

# vxedit -g -rf rm

4. Edit the .config file to reset the desire flag using any text editor.

active=off

forceminor=off

badlog=on <===== This flag should be edited to 'badlog=off'.

recover=off

krecover=off

invalid=off

recover_checkpoint=0

cdsrecover_seqno=0

cdsrecover_active=0

lasterr_tid=0.0

sd_num=0

sdnum=0

nvollayer=1

5. Recreate the volume configuration using the edited configuration file.

# vxmake -g -d .config

6. Start recreated Volume

# vxvol -g start
# vxvol -g start

7. Mount File system

Note: it is better to dump volume config before follow the procedure.
EG:
/etc/vx/diag.d/vxprivutil dumpconfig /dev/dsk/c4t50060E80102A00F0d8s3 > /tmp/OLS_TDS_DG05.config
/etc/vx/diag.d/vxprivutil dumpconfig /dev/dsk/c3t50060E80102A0082d3s3 > /tmp/OLS_TDS_DG02.config

ITPub博客

how to fix DCO BADLOG

最新文章