lvm migrations

[Simon_G]

I was doing lvm migrations on RAC clusters which had some shared storage (pvmove). After the migrations are done everything is fine (ASM disks). The problem is the original lvm disks mounted only on each individual node were zoned to all node in the cluster, So lvm is able to see all the vg's even the one from other servers. Here is what i did on each node.

1. pvmove of the vg's mounted on each node.

2. vgreduce and pvreduce on the same node only.

with the old storage removed i was hoping to powermt check and remove the dead paths, but i am not able to do this. I am not able to remove the dead pathsfrom one node to the old storage of a vg that was mounted on another node.In otherwords the paths from the node to the old storage that was mounted on itself has been removed perfectly but the path to the other storage that is the problem. Is there a way to fix this dead paths issue without reboot? These are Redhat 5.9 boxes.

Simon

[Matti_Kurkela]

You should be able to remove any old /dev/sd* paths by using the /sys filesystem.

For example, to tell the system that /dev/sdX is gone for good and should be forgotten, you would do:

echo 1 > /sys/block/sdX/device/delete

It's been a long time since I had PowerPath on any Linux system, but after removing the dead /dev/sd* paths, I would try "powermt check" again if necessary.

[Simon_G]

so the device /dev/sdau is showing as a dead path in powermt display and i offline the device using echo and then delete the device using the same echo command you provided and guess what the server panicked and rebooted. I also was looking at the online storage config guide and the same steps were mentioned and i am not sure why it panicked for a device that was offlined and removed. Any ideas?

Simon

[Matti_Kurkela]

Hmm... did the panic message get recorded into the system log? If it did, it might include a kernel stack trace that should be useful in understanding the problem.

What's your PowerPath version, anyway? If it is not the latest one, you might want to check the Release Notes of versions newer than you are currently using, and see if any relevant-looking bugs have been fixed in the newer versions.

[Simon_G]

It is 5.6 which is recent. We tried on 2 hosts and the same result. so we have decided to reboot and clear this dead path. It is really strange.

Simon