Memory Fault(coredump) - Bad memory?
Posted on 2009-04-07
I am doing a "vgscan -v" to try fixing some volume groups that won't activate after a hard shutdown. It runs for a few seconds then gives "Memory Fault(coredump)".
This might be related..... Previously I was getting this error, but fixed this by increasing the kernel parameter maxssiz from 8mb to 16mb:
received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
This may need another topic but what I need to do is activate 5 volume groups that are each giving these errors (disk resides on EMC Clarion):
"vgchange -a y /dev/vge28"
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c10t3d4":
vgchange: Warning: couldn't query physical volume "/dev/dsk/c10t3d4":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "/dev/vge28":
Quorum not present, or some physical volume(s) are missing.
"ioscan -fn" confirms that the disk is there:
disk 71 8/12/1/0.98.4.19.0.3.4 sdisk CLAIMED DEVICE DGC CX700WDR5
"strings /etc/lvmtab" looks correct: