Hi friends,
the paging lv hd6 is in stale condition
hd6 paging 48 96 2 open/stale N/A
And i'am getting the following alerts in the server
333BD283 0811044814 U S LVDD Bad block detected with no relocation al
333BD283 0811041114 U S LVDD Bad block detected with no relocation al
333BD283 0811040614 U S LVDD Bad block detected with no relocation al
03913B94 0810230414 U H LVDD HARDWARE DISK BLOCK RELOCATION ACHIEVED
E86653C3 0810230414 P H LVDD I/O ERROR DETECTED BY LVM
49A83216 0810230414 T H hdisk1 DISK OPERATION ERROR
03913B94 0810200614 U H LVDD HARDWARE DISK BLOCK RELOCATION ACHIEVED
E86653C3 0810200614 P H LVDD I/O ERROR DETECTED BY LVM
49A83216 0810200614 T H hdisk1 DISK OPERATION ERROR
Also when i'am doing syncvg -v rootvg i'am getting the below error,
0516-1296 lresynclv: Unable to completely resynchronize volume.
The logical volume has bad-block relocation policy turned off.
This may have caused the command to fail.
0516-934 /usr/sbin/syncvg: Unable to synchronize logical volume hd6.
kindly suggest what i have to do to bring the hd6 to syncronized state.
sysdumpdev -l
primary /dev/sysdmp_a
secondary /dev/sysdmp_b
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump FALSE
dump compression ON
The rootvg is in mirrored state.
Just for the record: "stale" means you have two (or more) mirror copies of a logical volume of which one (or more) are missing.
333BD283 0811044814 U S LVDD Bad block detected with no relocation al
333BD283 0811041114 U S LVDD Bad block detected with no relocation al
333BD283 0811040614 U S LVDD Bad block detected with no relocation al
03913B94 0810230414 U H LVDD HARDWARE DISK BLOCK RELOCATION ACHIEVED
Now, this is most probably the cause of your problems: when a physical disk is being formatted several blocks are set aside as spare. Should one allocated disk block become unreliable for some reason (the magnetic coating becomes defective somehow), then the driver automatically marks this block as "bad" and uses one of the set aside spare blocks instead. The data from the old block are transferred to the new location if this is still possible. This is called "bad block relocation".
0516-1296 lresynclv: Unable to completely resynchronize volume.
The logical volume has bad-block relocation policy turned off.
This may have caused the command to fail.
0516-934 /usr/sbin/syncvg: Unable to synchronize logical volume hd6.
hd6 is your swap and swap is basically memory. You do not want to tinker with the memory while the system is running, so there is a rationale behind this. But because bad block relocation is turned off, the system in turn cannot reloctae the block and therefore you have a stale LV.
My suggestion is to remove the stale mirror from the LV and then remirror it. Once the bad block is not any more part of an LV it will simply be marked as bad and not be used again should the surrounding space be reallocated to another LV.
I hope this helps.
bakunin