Operating System - HP-UX
1829103 Members
2268 Online
109986 Solutions
New Discussion

Adding volume groups on 2 hosts, same drives.

 
MarkW_1
Regular Advisor

Adding volume groups on 2 hosts, same drives.

The IS dept. just received 1 L class, 1 N class box supportin fc60 controller with 10 luns of raid 0/1 drives (60). Using SAM, set up volume groups for all drives. Decided to do the same thing on the L. This process overwrote data. Finally cleaned up lvmtab on both boxes. Cannot recreate vg02. I get a vgcreate error that a volume group is already using this major and minor number. Please check the minor number of the group device file. I need help to clean this up. Also, I am assuming from other responses that I will need to use vgimport/export to handle this. Thnx
4 REPLIES 4
Cheryl Griffin
Honored Contributor

Re: Adding volume groups on 2 hosts, same drives.

You are correct, vgexport will remove the device files for the volume group and it will update the /etc/lvmtab.
"Downtime is a Crime."
Cheryl Griffin
Honored Contributor

Re: Adding volume groups on 2 hosts, same drives.

Mark,
Depending on what has already been done to clean up the /etc/lvmtab, vgexport may give you errors.

The errors might indicate that the devices in /dev/vgXX still exists and these need to be cleaned up.

More specific answers could be given if we knew more about what you did and the status of the system, any errors, etc.
"Downtime is a Crime."
MarkW_1
Regular Advisor

Re: Adding volume groups on 2 hosts, same drives.

The cleanup process included running vgscan after deleting the lvmtab file. I also removed the volume files and vgXX directories, except vg00. Went back into SAM and tried to add the group. This is where I got the error. The group directory and volume were physically created for vg02 but not in SAM. AS a side note, 2 luns were moved to a different controller.
John Palmer
Honored Contributor

Re: Adding volume groups on 2 hosts, same drives.

Hi Mark,

The lesson to be learnt from this is never to use SAM for volume management when shared drives are involved - it's just not aware of the other server(s). Personally, I always write small scripts to create VG's and volumes. They are handy for reuse, useful for disaster recovery and provide some measure of documentation.

Regards,
John