topic Re: VG device file's minor alleged to be in use in Operating System - HP-UX

VG device file's minor alleged to be in use

Ralph Grothe — Mon, 29 Sep 2003 08:32:29 GMT

Hi,

WARNING -
I have been experiencing very annoying servicing problems of ITRC forums for the last week or so.
So I have some concern whether I will be able to read this thread after having submitted it at all.
They must have refurbished the website which had the effect of making most of it now inaccessible to my user agent (i.e. Netscape 4.75, cannot get a more recent binary for AIX, which is the OS of our login server :-(
When I follow a thread, all I get serviced/displayed are some buttons but no content whatsoever.
Thus I might not be able to give feedback as quickly as I wished.

Now to my subject.
I've been asked by my admin colleague to check the LVM consistency with regards to service guard on his cluster servers, since he had been doing quite some disk reconstruction work there lately.

The first thing I stumbled over was that vg00 denied vgdisplay because of supposed minor No. collision with other VGs' group devices.

# vgdisplay vg00
vgdisplay: Couldn't query volume group "vg00".
Possible error in the Volume Group minor number; Please check and make sure the
group minor number is unique.
vgdisplay: Cannot display volume group "vg00".

Hm, that's really strange because I cannot confirm this by stat'ing the device files (please, don't ask me why the gap between 0x1b000 and 0x1e0000)

# ll /dev/vg*/group|sort -n +6
crw-r----- 1 root sys 64 0x000000 Oct 19 1999 /dev/vg00/group
crw-r--r-- 1 root sys 64 0x010000 Nov 2 2000 /dev/vg01/group
crw-r--r-- 1 root sys 64 0x020000 Sep 4 14:55 /dev/vg02/group
crw-r--r-- 1 root sys 64 0x030000 Jun 13 2002 /dev/vg03/group
crw-r--r-- 1 root sys 64 0x040000 Nov 13 2000 /dev/vg25n/group
crw-r--r-- 1 root sys 64 0x050000 Sep 10 15:55 /dev/vg31n/group
crw-r--r-- 1 root sys 64 0x060000 Nov 13 2000 /dev/vg32n/group
crw-r--r-- 1 root sys 64 0x070000 Sep 10 15:57 /dev/vg33n/group
crw-r--r-- 1 root sys 64 0x080000 Nov 13 2000 /dev/vg34n/group
crw-r--r-- 1 root sys 64 0x090000 Sep 16 14:47 /dev/vg35n/group
crw-r--r-- 1 root sys 64 0x0a0000 Nov 13 2000 /dev/vg36n/group
crw-r--r-- 1 root sys 64 0x0b0000 Nov 13 2000 /dev/vg37n/group
crw-r--r-- 1 root sys 64 0x0c0000 Sep 16 14:47 /dev/vg38n/group
crw-r--r-- 1 root sys 64 0x0d0000 Nov 13 2000 /dev/vg39n/group
crw-r--r-- 1 root sys 64 0x0e0000 Nov 13 2000 /dev/vg40n/group
crw-r--r-- 1 root sys 64 0x0f0000 Sep 18 15:45 /dev/vg41n/group
crw-r--r-- 1 root sys 64 0x100000 Sep 29 09:15 /dev/vg42n/group
crw-r--r-- 1 root sys 64 0x110000 Sep 11 15:04 /dev/vg04/group
crw-r--r-- 1 root sys 64 0x120000 Feb 7 2001 /dev/vg12n/group
crw-r--r-- 1 root sys 64 0x130000 Jul 31 10:36 /dev/vg11n/group
crw-r--r-- 1 root sys 64 0x140000 Nov 15 2002 /dev/vg30/group
crw-r--r-- 1 root sys 64 0x150000 Jul 19 2002 /dev/vg9tmp/group
crw-r--r-- 1 root sys 64 0x160000 Jul 15 10:36 /dev/vg05/group
crw-r--r-- 1 root sys 64 0x170000 Sep 19 14:31 /dev/vg05d/group
crw-r--r-- 1 root sys 64 0x180000 Sep 28 12:19 /dev/vg11d/group
crw-r--r-- 1 root sys 64 0x190000 Sep 22 14:55 /dev/vg25d/group
crw-r--r-- 1 root sys 64 0x1b0000 Sep 23 09:23 /dev/vg12d/group
crw-r--r-- 1 root sys 64 0x1e0000 Sep 27 19:10 /dev/vg30d/group
crw-r--r-- 1 root sys 64 0x2b0000 Sep 19 2001 /dev/vg50/group
crw-rw-rw- 1 root sys 64 0x1a0000 Sep 17 12:36 /dev/vg50d/group

This crashes also

# lvlnboot -v vg00
lvlnboot: Couldn't query volume group "/dev/vg00".
Possible error in the Volume Group minor number; Please check and make sure the
group minor number is unique.

But at least I can retrieve the backed up LVM data of this vg

# vgcfgrestore -f /etc/lvmconf/vg00.conf -l
Volume Group Configuration information in "/etc/lvmconf/vg00.conf"
VG Name /dev/vg00
---- Physical volumes : 2 ----
/dev/rdsk/c1t6d0 (Bootable)
/dev/rdsk/c2t6d0 (Bootable)

which matches this

# strings /etc/lvmtab|head -5
/dev/vg00
%d"88
/dev/dsk/c1t6d0
/dev/dsk/c2t6d0

Looks to me that my fellow admin's messing with the disks has somehow created yet another wee kernel vs. user space LVM inconsistency.

Any suggestions?

Rgds.
Ralph

Re: VG device file's minor alleged to be in use

Ralph Grothe — Mon, 29 Sep 2003 08:35:26 GMT

Ouch,
I can see my posting, but either the webserver has sent me or my user agent has displayed a whole mess.
No formatting or aiding whitespace to support readebility.
I hope you don't get the same clutter.

Re: VG device file's minor alleged to be in use

Ralph Grothe — Mon, 29 Sep 2003 08:36:41 GMT

Nay, now I only can see the buttons again...

HELP!

Re: VG device file's minor alleged to be in use

Tom Geudens — Mon, 29 Sep 2003 08:44:31 GMT

Hi Ralph,
You could try the following to see what vgscan suggests ...
#vgscan -p

Regards,
Tom Geudens

Re: VG device file's minor alleged to be in use

RolandH — Mon, 29 Sep 2003 08:46:35 GMT

Hi Ralph,

try a ll /dev/*/group.

Perhaps you have other places then in vg* dir, where a group file is stored.

Roland

Re: VG device file's minor alleged to be in use

Michael Steele_2 — Mon, 29 Sep 2003 09:03:09 GMT

Regarding:

# strings /etc/lvmtab|head -5
/dev/vg00
%d"88
/dev/dsk/c1t6d0
/dev/dsk/c2t6d0

The "...%d"88..." is normal. I've read where its the encrypted vgid and know that it is suppose to be there.
##########################################
#
##########################################

Regarding:

"...crw-r----- 1 root sys 64 0x000000 Oct 19 1999 /dev/vg00/group..."

Shoud the permission be the same as the others? "...crw-r--r---..."
############################################
#
############################################
Also refer to this patch: PHCO_21630

Referenced in this thread:
http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0xad338f960573d611abdb0090277a778c%2C00.html&admit=716493758+1064843859426+28353475
############################################
#
############################################
Finally, you may be losing a O/S disk, /dev/dsk/c1t6d0 or /dev/dsk/c2t6d0 or a SCSI controller, c2 or c1. Refer to LOGTOOL, ioscan (* NO_HW *) and syslog.log. Also '...dd...' the disks:

dd if=/dev/dsk/c1t6d0 of=/dev/null count=1000000

Attach the results from logtool:

STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY

Re: VG device file's minor alleged to be in use

Ralph Grothe — Mon, 29 Sep 2003 09:06:37 GMT

Sorry friends,
I have well noticed that two responses to my thread were posted but I simply cannot read them.

WEBMASTERS HELP!

I can only see thread listings on a section's main page.
Nice that you have included more table columns that show you also how many replies came in, and when this happened.
But what's that worth for if I cannot read the replies because all I can see are reply and back buttons and the like! :.-{

Re: VG device file's minor alleged to be in use

Ralph Grothe — Mon, 29 Sep 2003 09:41:54 GMT

Ok, I'm back with you.
Grr, I hate being forced to use Windoze Internet Exploder.
That's the User Agent I unwillingly chose right now.
It's not funny that web developers drop support for ole Mozilla in favour of IE.
Come on this is a Unix Website.
Why on earth should we be forced to use M$ clients?

Now that I can read your replies I can check the recipes and respond.

Roland,

I changed my globbing pattern as you suggested, but I didn't miss out presumably differently named vgs with my first vg* globbin.
The result (i.e. No. of devices) is the same, but good hint anyway.

Btw another annoying result of the usage of IE is that I have to clumsely cut and paste to Windoze's clipboard from Exceed's.
Many more mouse clicks than before.
(I don't like mice either)

Michael,

I "chmod o+r /dev/vg00/group", but vgdisplay keeps complaining.
Anyway I issued it as root before.

All my disks seem claimed.

# ioscan -FCdisk|grep NO_HW
# ioscan -kFCdisk|grep -v CLAIMED
#

The reading of 100 MB from the raw devs don't give evidence of broken disks either.

# vgcfgrestore -f /etc/lvmconf/vg00.conf -l
Volume Group Configuration information in "/etc/lvmconf/vg00.conf"
VG Name /dev/vg00
---- Physical volumes : 2 ----
/dev/rdsk/c1t6d0 (Bootable)
/dev/rdsk/c2t6d0 (Bootable)
# dd if=/dev/rdsk/c1t6d0 of=/dev/null bs=1024k count=100
100+0 records in
100+0 records out
# dd if=/dev/rdsk/c2t6d0 of=/dev/null bs=1024k count=100
100+0 records in
100+0 records out

Re: VG device file's minor alleged to be in use

Ralph Grothe — Mon, 29 Sep 2003 09:49:11 GMT

Roland,

how did you manage to get lines of whitespace in your reply?

It looks as if the Webserver's CGI, servlet or whatever is removing any white lines from posts before inserting them in the database's tables.

Is client supplied HTML markup supported by now?
I mean would this

give me a new paragraph?

Re: VG device file's minor alleged to be in use

Ralph Grothe — Mon, 29 Sep 2003 09:53:38 GMT

Tom,

besides many warnings (none of which relate to the disks in vg00) I get these inabilities to stat disks.

# vgscan -p 2>&1 >/dev/null|grep stat
Couldn't stat physical volume "/dev/dsk/c0t1d0":
Couldn't stat physical volume "/dev/dsk/c8t10d0":
Couldn't stat physical volume "/dev/dsk/c8t11d0":
Couldn't stat physical volume "/dev/dsk/c8t12d0":
Couldn't stat physical volume "/dev/dsk/c8t13d0":
Couldn't stat physical volume "/dev/dsk/c8t14d0":
Couldn't stat physical volume "/dev/dsk/c8t15d0":

Re: VG device file's minor alleged to be in use

RolandH — Mon, 29 Sep 2003 09:53:54 GMT

You get white line with

That is a workaround I use, since HP has changed this.

Roland

Re: VG device file's minor alleged to be in use

Mark Grant — Mon, 29 Sep 2003 10:01:41 GMT

Ralph,

Latest Mozilla does actually work with this site (posting with it now) and typing a space gives you a blank line.

Don't think I can help on your possible non unique minor number except (and this is a long shot) I'm not sure if you would get this if you set number of volume groups kernel paramater to say 20, created 20 volume groups and then reduced the kernel parameter again.

I think I'm right in saying that if you try to exceed the maximum number of volume groups it says "non unique minor numbre"

Re: VG device file's minor alleged to be in use

RolandH — Mon, 29 Sep 2003 10:06:13 GMT

Another hint,

what kind of disc reconstruction has "your colleague" done.
A stupid question from me: Is the maxvgs kernel parmeter higher than you are using. Was a crash there and perhaps he has booted from a old kernel with a lower integer for the parameter.

Are you able to mount all vg?

Roland

Re: VG device file's minor alleged to be in use

Michael Steele_2 — Mon, 29 Sep 2003 11:22:23 GMT

Regarding:

# vgscan -p 2>&1 >/dev/null|grep stat
Couldn't stat physical volume "/dev/dsk/c0t1d0":

This is probably something like a optical juke box. Use 'dd' to test if not.
###########################################
#
###########################################
Regarding:

# dd if=/dev/rdsk/c1t6d0 of=/dev/null bs=1024k count=100
100+0 records in
100+0 records out

Count needs to be 1000000, not 100, or you're hitting the cache and not the disk.
###########################################
#
###########################################

There is no more reliable HW diagnostic tool then logtool, please attach:

STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY
###########################################
#
###########################################
Read your bootlif

lifls /dev/rdsk/c1t6d0
lifcp /dev/rdsk/c1t6d0:AUTO -

###########################################
#
###########################################
What messages with the following?

lvlnboot -R

###########################################
#
###########################################

Remake /etc/lvmtab.

cp /etc/lvmtab dir/lvmtab_old

vgscan -p -a -v (* preview *)

vgscan -a -v (* when ready *)
###########################################
#
###########################################

This thread indicates vgid on disk and vgid in /etc/lvmtab don't match, so again, remake /etc/lvmtab.

http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0xad338f960573d611abdb0090277a778c%2C00.html&admit=716493758+1064852450993+28353475

Re: VG device file's minor alleged to be in use

Ralph Grothe — Tue, 30 Sep 2003 02:15:27 GMT

Good Morning again (at least on this side of the pond).

To those who asked for the kernel parameter influencing vg creation:

# /usr/sbin/kmtune -q maxvgs
Parameter Value
===============================================================================
maxvgs 80
# ls /dev/*/group|wc -l
30
# strings /etc/lvmtab|grep vg|wc -l
29

Michael,

the root/boot disks are only 17 GB.
Since I read 1 MB blocks your suggested million counts would make up some 1 TB if I haven't slipped over my crude arithmetics here.
Thus I hope, to cirmumvent buffer cache some 10 Gigs read should suffice.

# diskinfo /dev/rdsk/c2t6d0
SCSI describe of /dev/rdsk/c2t6d0:
vendor: SEAGATE
product id: ST318203LC
type: direct access
size: 17783240 Kbytes
bytes per sector: 512
# timex dd if=/dev/rdsk/c2t6d0 of=/dev/null bs=1024k count=$((1024*10))
10240+0 records in
10240+0 records out

real 7:21.06
user 0.11
sys 3.46

Re: VG device file's minor alleged to be in use

RolandH — Tue, 30 Sep 2003 02:44:42 GMT

Hi Ralph,

I see you are using "html tags" ""
That was not meant.
I mean hit space bar and then return for a white line.
But your attempts a funny to see. Hi Hi

Roland

No

points

please

!!!

Re: VG device file's minor alleged to be in use

Jakes Louw — Tue, 30 Sep 2003 03:15:11 GMT

Ralph

Do a "vgchange -a y /dev/vg00".
This SHOULD get the kernel and LVM back in step. The only other option is a reboot, to flush the kernel tables....

Re: VG device file's minor alleged to be in use

Michael Steele_2 — Tue, 30 Sep 2003 03:54:02 GMT

Gee, I guess so.

1024x1024x1024 bytes = what? What is 1024x1024x1024????

1 GB or 1,073,741,824 bytes

@ 512 bytes per raw block when count=1000000 you get what?

512,000,000 bytes

Hmmmmmm, Lop off all the trailing zeros.....
for 512 or 1,073 and which is bigger?

Ralph, stand in front of the disk and watch for the read LED to light up. Does it light up when count=100 ? No.

No one ever sits through a whole 1,000,000 count. They wait for the read LED to light up, or not, and 'control c' out.

*PS - psssst - Try it on a good disk first.

:-)

Re: VG device file's minor alleged to be in use

Ralph Grothe — Tue, 30 Sep 2003 07:27:22 GMT

Roland,

you're right.
I'm an idiot.
Got right this time that shouldn't be taken verbatim.

Jake,

# vgchange -a y /dev/vg00
vgchange: Couldn't set the unique id for volume group "/dev/vg00":
File exists
# vgdisplay /dev/vg00
vgdisplay: Couldn't query volume group "/dev/vg00".
Possible error in the Volume Group minor number; Please check and make sure the
group minor number is unique.
vgdisplay: Cannot display volume group "/dev/vg00".

Michael,

I've never used this Logtool Submenu within STM so far.

This I got following your instructions

-- Logtool Utility: View Raw Summary --

Summary of: /var/stm/logs/os/log3.raw.cur

Date/time of first entry: Tue Mar 12 13:24:25 2002

Date/time of last entry: Wed Sep 3 17:11:24 2003

Number of LPMC entries: 0
Number of System Overtemp entries: 0
Number of LVM entries: 0
Number of Logger Event entries: 5

Number of I/O Error entries: 254

But I can be more specific in posting the error logs of the root disks.

# lssf $(vgcfgrestore -f /etc/lvmconf/vg00.conf -l|awk '/rdsk/{print$1}')|awk '{print $(NF-1)}'
0/0/2/0.6.0
0/0/2/1.6.0

# echo "sel path 0/0/2/0.6.0 0/0/2/1.6.0;info;wait;il"|/usr/sbin/cstm

-- Information Tool Log for SCSI Disk on path 0/0/2/0.6.0 --

Log creation time: Tue Sep 30 11:57:29 2003

Hardware path: 0/0/2/0.6.0

Product Id: ST318203LC Vendor: SEAGATE
Device Type: SCSI Disk Firmware Rev: HP01
Device Qualifier: SEAGATEST318203LC Logical Unit: 0
Serial Number: LR789981000010210EBU
Capacity (M Byte): 17366.45
Block Size: 512
Max Block Address: 35566479
Error Logs
Read Errors: 0 Buffer Overruns: N/A
Read Reverse Errors: N/A Buffer Underruns: N/A
Write Errors: 0 Non-Medium Errors: 0
Verify Errors: 0

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for SCSI Disk on path 0/0/2/1.6.0 --

Log creation time: Tue Sep 30 11:57:29 2003

Hardware path: 0/0/2/1.6.0

Product Id: ST318203LC Vendor: SEAGATE
Device Type: SCSI Disk Firmware Rev: HP01
Device Qualifier: SEAGATEST318203LC Logical Unit: 0
Serial Number: LR07964600001934JHNC
Capacity (M Byte): 17366.45
Block Size: 512
Max Block Address: 35566479
Error Logs
Read Errors: 0 Buffer Overruns: N/A
Read Reverse Errors: N/A Buffer Underruns: N/A
Write Errors: 0 Non-Medium Errors: 0
Verify Errors: 0
-- Information Tool Log for each selected device --
View - To View the file.
Print - To Print the file.
SaveAs - To Save the file.
Enter Done, Help, Print, SaveAs, or View: [Done] #.

As for my mistaken block count.
Yes, you're calculations are better than mine.
I always lose dimension when being faced with too many zeros.
That's why I prefer scientific notation with big numbers like 1e+09

So here are the million blocks read from the root/boot disks

# timex dd if=/dev/rdsk/c1t6d0 of=/dev/null count=1000000
1000000+0 records in
1000000+0 records out

real 3:46.36
user 1:16.92
sys 50.87

# timex dd if=/dev/rdsk/c2t6d0 of=/dev/null count=1000000
1000000+0 records in
1000000+0 records out

real 3:22.79
user 1:15.10
sys 43.23

and the LIF headers

# lifls /dev/rdsk/c[12]t6d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO HPUX ISL
AUTO LABEL

ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO ISL AUTO
HPUX LABEL

# for c in 1 2;do lifcp /dev/rdsk/c${c}t6d0:AUTO -;done
hpux
hpux (;0)/stand/vmunix

Oops, looks as if the should receive a quorum AUTO stirng such as "hpux -lq".

Btw, this is the output to "lvlnboot -R".
I think I should ask my colleague about his recent disk settings ;-)

# lvlnboot -R
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t0d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t10d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t10d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t11d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t11d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t11d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t11d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t11d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t11d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t12d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t13d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t13d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t13d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t13d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t13d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t13d3":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t13d4":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t13d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t13d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t13d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t6d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t6d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t6d3":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t12d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t12d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t12d3":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t12d4":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t12d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t12d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t12d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t13d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t13d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t13d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t13d3":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t13d4":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t1d4":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t1d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t1d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t1d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t2d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t2d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t2d3":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t2d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t2d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t2d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t3d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t3d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c5t3d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t10d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t11d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t11d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t11d3":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t11d4":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c4t11d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t1d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t1d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t2d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t2d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t2d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t2d3":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t2d4":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t2d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t8d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t5d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t3d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t3d3":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t6d4":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t6d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t8d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t8d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t8d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t9d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t8d3":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t8d4":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t0d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t0d2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t0d3":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t0d4":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t0d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t0d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t0d7":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t1d0":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t1d1":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t3d4":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t3d5":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c8t3d6":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
vgcfgbackup: Volume group not activated.

Re: VG device file's minor alleged to be in use

Michael Steele_2 — Tue, 30 Sep 2003 13:28:12 GMT

I don't see anything to be concerned about. Earlier a response suggested that the kernel and current /etc/lvmtab could be resync'd with a reboot, and I believe this is probably the source of the vgdisplay messages. So try a reboot.