1833581 Members
4140 Online
110061 Solutions
New Discussion

Re: LVM error

 
Filosofo
Regular Advisor

LVM error

Hello
when I execute vgdisplay -v /dev/vg_sv I see:

vgdisplay: Cannot open the control file "/dev/vg_sv/group":
No such device
vgdisplay: Cannot display volume group "vg_sv".


This is output of ll /dev/vg_sv
total 0
crw-rw-rw- 1 root sys 64 0x0e0000 Apr 29 10:01 group
brw-r----- 1 root sys 64 0x0e0001 Apr 29 10:06 lv_sv
brw-r----- 1 root sys 64 0x0e0002 Apr 29 10:08 lv_sv_app
crw-r----- 1 root sys 64 0x0e0001 Apr 29 10:06 rlv_sv
crw-r----- 1 root sys 64 0x0e0002 Apr 29 10:08 rlv_sv_app

Please help

Filo
Sistem engeneer expert
12 REPLIES 12
Rita C Workman
Honored Contributor

Re: LVM error

Is the vg active??

vgchange -a y /dev/vg

Is it/or was it part of any MC/SG package?

vgchange -c n /dev/vg
vgchange -a y /dev/vg

Just a quick thought to try,
Rita
Ravi_8
Honored Contributor

Re: LVM error

Hi,

Looks like corrupted lvmtab file

#mv /etc/lvmtab /etc/lbmtab.old
#vgscan -a -v
#vgdisplay -v /dev/vg_sv
never give up
Balaji N
Honored Contributor

Re: LVM error

hi
by any chance lvmtab is corrupted.

1. vgchange -a y vgname.

2. mv /etc/lvmtab /etc/lvmtab.oriug.

3. vgscan -a -v -p (preview)

4. vgscan -a -v (recreate lvmtab)

hth
-balaji
Its Always Important To Know, What People Think Of You. Then, Of Course, You Surprise Them By Giving More.
Filosofo
Regular Advisor

Re: LVM error

gscan: has no correspoding valid raw device file under /dev/rdsk.
Verification of unique LVM disk id on each disk in the volume group
/dev/vg_sv failed.
Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c6t2d0
/dev/dsk/c8t2d0

Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c6t4d0
/dev/dsk/c8t4d0
Sistem engeneer expert
John Poff
Honored Contributor

Re: LVM error

Hi,

Your group file looks fine for that VG. Maybe you have a duplicate minor number for a group file on another VG? Try this:

ls -l /dev/*/group | sort -k6

and you should get a sorted list of all your group files. See if any have the same minor numbers.

JP
lanke_1
Advisor

Re: LVM error

Hi Filo,

What kind of storage do you have i..e is it an internal or external disk.

How many volume groups are there on this particular disk
device.

Are you able to mount the File systems with logical volumes on this vg_sv.

Thanks,
Lanke



Cheryl Griffin
Honored Contributor

Re: LVM error

What is your maxvgs set to?
# sysdef |grep maxvgs

Could it be that the maxvgs is set to low and this group 0x0e exceeds that value? 0x0e would be 15 (if I am counting correctly).
# ll /dev/vg* |grep group |wc -l
# ll /dev/vg*|grep group
"Downtime is a Crime."
Bill McNAMARA_1
Honored Contributor

Re: LVM error

strings /etc/lvmtab before vgscanning.
you can vgimport if the activation doesn't work.

the vgscan can screw up all alternate path 'load balancing' that may have been configured. If you don't know what a pvlink is then the vgscan possibly won't screw this up, unless of course you didn't create the lvm conf!

Later,
Bill
It works for me (tm)
lanke_1
Advisor

Re: LVM error

I'm sure that same minor number has been used for two
group files.

If you have the map file,
I would suggest you do the
vgexport and vgimport process
again to create vg_sv.

Thanks,
Lanke





omars
Advisor

Re: LVM error

Hi ,

a.) I assume your /dev/vg_sv
files are okay .
If not execute
mknod /dev/vg_sv/group c 64 0x0e0000
mknod /dev/vg_sv/lv_sv c 64 0x0e0001
mknod /dev/vg_sv/lv_sv_app c 64 0x0e0002
mknod /dev/vg_sv/rlv_sv c 64 0x0e0001
mknod /dev/vg_sv/rlv_sv_app c 64 0x0e0002

b.) Next do
vgdisplay /dev/vg_sv
If u get errors , then proceed to step c

b.) sam --> kernel configuration-->Configurable parameters

select "maxvgs" and set to 15
and modify Kernel .
System will automatically reboot

d.)Once system is up & running , then do
vgscan -v ( recreate -lvmtab )

e.) Now u can do
vgchange -a y /dev/vg_sv

f.)mount -a
This will mount your lvols .



Nothing is too late to learn
V. V. Ravi Kumar_1
Respected Contributor

Re: LVM error

Hi,
I think this is the problem of having duplicate minor numbers for group files. run
ll /dev/*/group
this show group files for all VG's, check for any duplication and change it.
delete present group file and create a new one with different minor number

mknod /dev/vg_sv/group c 64 0x0006

Regards
Never Say No
omars
Advisor

Re: LVM error

Hi Ravi ,

Using a unique group device will
not help at all because the physical volumes in "vg_sv" have PVRA & VGRA
areas which indicates the mapping
of 0x0e0000

rgds

Nothing is too late to learn