topic Re: moving disk in Operating System - HP-UX

moving disk

hpuser_6 — Tue, 29 Apr 2003 20:22:59 GMT

moving from point to point topology to arbitarate loop, would vgscan update the lvmtab after running insf -e and ioscan for the new h/w path. Do I still need to make a mapfile for later vgimport. I do not want to destroy the information or alter the information in any volume group...

Re: moving disk

John Dvorchak — Tue, 29 Apr 2003 20:35:07 GMT

I think to be on the safe side you would:

vgexport -v -s -m /tmp/mapfile vgxx

and then to import it:

vgimport -m /tmp/mapfile -s vgname

or

vgimport -m /tmp/mapfile vgname /dev/dsk/c_t_d_

The "s" option writes the vg serial number to the disk but be warned if you have a lot of disks it will look at everyone of them on the import. Since only one disk you may still want to export it with the s just in case but import it with the path name.

Re: moving disk

John Dvorchak — Tue, 29 Apr 2003 20:36:47 GMT

Ok my fault I had a serious typo:

vgexport -p -v -m /tmp/mapfile -s vgname

DONT FORGET THE -P OPTION.

Sorry about that

Re: moving disk

hpuser_6 — Tue, 29 Apr 2003 20:43:37 GMT

if the old disk from point to point topology is as /dev/dsk/c1t3d0, now it has changed to /dev/dsk/c3t3d0 because of changing the topology. will vgimport knows that these are the same physical devices and the only thing it changes is the h/w path??

Re: moving disk

John Dvorchak — Tue, 29 Apr 2003 21:14:46 GMT

Correct if you vgexport -p -m /tmp/mapfile then it will know on the import because you will use both the map file and the new hardware path.

vgexport -v -p -s -m /tmp/mapfile vgxx

Will create the mapfile with the lv info and serialize it.

vgimport -m /tmp/mapfile vgyy /dev/dsk/c3t3d0

now the vg name has to be different, cause if you just export the vg to erase it, it will also remove the lv info from the disk.

I am assuming that this is on the same system and not moving to a different system.

Re: moving disk

Michael Steele_2 — Tue, 29 Apr 2003 21:16:13 GMT

Regarding: "...if the old disk from point to point topology is as /dev/dsk/c1t3d0, now it has changed to /dev/dsk/c3t3d0 because of changing the topology. will vgimport knows that these are the same physical devices and the only thing it changes is the h/w path?? ..."

This is a very good question.

Its my understanding that Arbitrated loop is a SAN topology. Is this topology changing from the switch or the disk array? If disk array are the luns being redefined? If the luns aren't being redefined and its just a topology change, especially a topology change via the switch, then no.

However you are indicating a change, from c1t3d0 to c3t3d0. Is this speculation of fact?

Need more information. What's your disk array? How are you changing your topology? Is there a switch?