1834647 Members
2109 Online
110069 Solutions
New Discussion

Re: vgimport

 
Alexander Yereshenko
Frequent Advisor

vgimport

How can i fix this problem?
# Beginning the import process on Volume Group "/dev/vgu22".
vgimport: Cannot open the control file "/dev/vgu22/group":
No such device
11 REPLIES 11
Shrikant Lavhate
Esteemed Contributor

Re: vgimport

I guess you need to have device name into command not volume group name.

you need to input the device name like this

vgimport -v -m mapfile /dev/dsk/cXtXdX
Will it remain a personal, if I broadcast it here!
Shrikant Lavhate
Esteemed Contributor

Re: vgimport

Where map file consist of which Logical Volume
names and numbers are to be read. See manpage for details.
Will it remain a personal, if I broadcast it here!
Alexander Yereshenko
Frequent Advisor

Re: vgimport

i have not imported volume groups
Shrikant Lavhate
Esteemed Contributor

Re: vgimport

> i have not imported volume groups

What you mean by this? You havnt runned any command? then from where you got above error.... From log files??
Will it remain a personal, if I broadcast it here!
A. Clay Stephenson
Acclaimed Contributor

Re: vgimport

Before executing vgimport, you must first create a directory (/dev/vgu22 in this case) and a device node, /dev/vgu22/group.

First, do an "ls -l /dev/vg*/group" and note all the minor device numbers in use. Choose a unused one, e.g. 0x090000 and make the device node.

mknod /dev/vgu22/group c 64 0x090000

You can them execute vgimport. The map file is optional if the LVOL names are standard and you know the disk device nodes.
If it ain't broke, I can fix that.
rajdev
Valued Contributor

Re: vgimport

Hi,

Agree to what Clay has said, the man page of vgimport is clear about it .....

From #man vgimport --->
The command works much like vgcreate by requiring that the volume group device directory and the group special file be created before the command is executed.


Regards,
RD
Alexander Yereshenko
Frequent Advisor

Re: vgimport

# mknod /dev/vgu12/group c 64 0x110000
# vgimport -v /dev/vgu12 /dev/dsk/c14t1d3
Beginning the import process on Volume Group "/dev/vgu12".
vgimport: Cannot open the control file "/dev/vgu12/group":
No such device

--it still same situation
Hasan  Atasoy
Honored Contributor

Re: vgimport

hi alexander;

hp-ux has a kenel parameter, maxvgs, you cannot give group number greater than this value. look at maxvg parameter by "kctune maxvg" and give a value less than this value.

Hasan.
rajdev
Valued Contributor

Re: vgimport

Hi Alexander,

1. check maxvgs as told by hasan and increase it if its the default (10 ).

2. how many Volume groups do you already have

cd /dev
ls -lR|grep group|sort -n -k6

then add 1 to the minor number of the last entry and create the group file with that number ..

a) see that you don't have a vgu22 volume group already existing ...!
b) mkdir -p /dev/vgu22
c) mknod /dev/vgu22/group c 64 0x??0000

replace ?? with the number you calculated in step 2 above

d) now try the import -- use the verbose option
e) if you still have problem .. use tusc command when running vgimport

Regards,
RD
Nguyen Anh Tien
Honored Contributor

Re: vgimport

I think you set vgs (in kernel parameter) to 10 and then you create group file with minor number is 0x110000 so system does not recognize
Pls increate vgs to 15 or 20 or change minor number below 9
#mknod /dev/vg02/group c 64 0x080000
HTH
tienna
HP is simple
A. Clay Stephenson
Acclaimed Contributor

Re: vgimport

... and note that rather than using 0x110000 you probably want to use 0x0b0000 but you need to choose an unused minor device number that is less than maxvgs (and note that maxvgs is usually specified as a decimal number).
If it ain't broke, I can fix that.