Stale extents..contd

[joe_91]

This is in continuation to
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1036944

This is what happenend yesterday..as mentioned on my lvol1 i saw stale extents on the primary boot disk (so needs to be replaced)..the machine was taken down and the CE pulled the c2t0d0 drive from the slot "0".(ioscan below)
# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DW-224E
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0

after he replaced the new drive, i got the bad lif error..suspecting he might have pulled the wrong drive(primary was bad), i asked him to revert the process and put the drive he pulled out into the same "0" slot and tried booting the machine came all the way up and also i did not see the stale extents on lvol1.

My question is
1. if the CE pulls the working disk instead of the BAD boot disk and inserts the new disk will we get a BAD LIF MAGIC error?

2. using ioscan's PATH how can i tell to pull the correct BAD disk out?

3. As in this case, will a reboot fix the stale extents issue? or did it do a vgsync since the drive was pulled out and put back?

Please Clarify.

Best Regards

Joe.

[Steven E. Protter]

1. Yes
2. You match the device on the stale extent and translate it back to the format that sea command uses. You can also identify the disk by running a short dd command on it and watching for the disk light to expand dd if=/dev/dsk/c2t1d0 of=/def/null bs=1024
3. lvsync will also work. A boot does involve an execution of lvsync or vgsync soon after the volume group is activated. If you have a disk problem this isn't going to work. It will fix a temporary problem caused by you for example pulling the plug on a disk.

SEP