Following copy at array level- one node lost vxconfigd upon being presented with diskgroup

  • Article ID:100004771
  • Modified Date:
  • Product(s):

Problem

Following copy at array level all 'vx' commands hang on one node of cfs cluster.

Error Message

Jan 21 11:16:55 ghdora3lds kernel: VxVM vxio V-5-3-1111 voldio: I/O Timedout on disk pillar-axiom0_80, 1 I/Os hung on the disk!
Jan 21 11:16:55 ghdora3lds kernel: VxVM vxio V-5-3-1112 voldio: I/O hung; disallowing all I/Os to the disk.
Jan 21 11:16:55 ghdora3lds kernel: VxVM vxio V-5-3-1110 voldio: Failed disabling I/Os to disk!
Jan 21 11:16:55 ghdora3lds kernel: VxVM vxdmp V-5-0-0 i/o error occured (errno=0x6) on dmpnode 201/0x430
Jan 21 11:16:55 ghdora3lds kernel:
Jan 21 11:16:56 ghdora3lds kernel: VxVM vxio V-5-3-1146 voldsio_timeout: Timeout value 240 seconds, actual io time 240 seconds, I/O Timedout, bad disk?
 

Cause

The one node had the disk errors reported, which was reason for vxconfigd hang. There have been issues found with the base 5.1 release, that since have been addressed.

Solution

Upgrade to either 5.1RP2 or 5.lSP1


Was this content helpful?

Get Support