Logical Volume listing wrong 1

[ksmith40]

Running SAM, when I list my Logical Volumes, I see (notable):
[tt]Log. Vol. Vol. Group Type Use Tot. MB Mirror Mount
lvol1 vg01 LVM Unused 17304 0
man1 vg01 LVM VxFS 17304 0 /man1
[/tt]

This is not everything on the VG, but the items pertaining to my question. The drive is a 36GB drive and all of the standard OS files are on vg00 which is on another 36GB drive. A Volume Group listing shows vg01 as having 7748 of 34724 MB available and 6 logical volumes. There are six logical volums if you exclude the "lvol1" one.

When I [tt]ls -l[/tt] on [tt]/dev/vg01[/tt] I see that [tt]lvol1, rlvol1, man1[/tt] and [tt]rman1[/tt] all share [tt]0x010001[/tt].

I cannot do anything with lvol1 even though it is annotated as unused. I've never seen anything like this. I looks like a "copy" of the man1 LV.

I'm trying to free up space on my drives and move some stuff around to make room for an ERP system upgrade, but it looks like something odd is going on. Any idea what I should do about this (ignoring it being an option, of course).

Any comments or advice would be appreciated? Thanks.

 

[Martin999]

I think ...

When I ls -l on /dev/vg01 I see that lvol1, rlvol1, man1 and rman1 all share 0x010001.

is correct, the lvols are on the same VG and this is signified as 0x01 ... Do a ll /dev/*/group and I suspect you'll find that the minor no. for vg01 is 0x010000

As a tip, don't use SAM, I have personally seen it screw up crontabs and kernels. Not recommeneded by any of my colleagues either.

M

 

[ksmith40]

Thanks for the reply. Here's what I get when I ll /dev/vg01:

[tt]# ll /dev/vg01
total 0
cr--r--r-- 1 root sys 64 0x010000 Jun 25 2004 group
br--r----- 1 root sys 64 0x010001 Jun 25 2004 lvol1
br--r----- 1 root sys 64 0x010005 Jul 23 2005 man0
br--r----- 1 root sys 64 0x010001 Jul 23 2005 man1
br--r----- 1 root sys 64 0x010006 Jul 23 2005 man3
br--r----- 1 root sys 64 0x010004 Jul 23 2005 mantemp
cr--r----- 1 root sys 64 0x010001 Jun 25 2004 rlvol1
cr--r----- 1 root sys 64 0x010005 Jul 23 2005 rman0
cr--r----- 1 root sys 64 0x010001 Jul 23 2005 rman1
cr--r----- 1 root sys 64 0x010006 Jul 23 2005 rman3
cr--r----- 1 root sys 64 0x010004 Jul 23 2005 rmantemp
cr--r----- 1 root sys 64 0x010002 Jul 23 2005 ru1
cr--r----- 1 root sys 64 0x010003 Jul 23 2005 ruvtemp
br--r----- 1 root sys 64 0x010002 Jul 23 2005 u1
br--r----- 1 root sys 64 0x010003 Jul 23 2005 uvtemp[/tt]

Notice that lvol1 and man1 both take 0x010001. Yet, lvol1 shows as unused.

vgdiplay gives:

[tt]
# vgdisplay -v vg01
--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 6
Open LV 7
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 8683
VGDA 2
PE Size (Mbytes) 4
Total PE 8681
Alloc PE 6744
Free PE 1937
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg01/lvol1
LV Status available/syncd
LV Size (Mbytes) 17304
Current LE 4326
Allocated PE 4326
Used PV 1

LV Name /dev/vg01/man1
LV Status available/syncd
LV Size (Mbytes) 17304
Current LE 4326
Allocated PE 4326
Used PV 1
[/tt]

(continued...)

The "Open LV" line is interesting.
What am I missing here? This is probably something common, but I haven't experienced it until now.

 

[Martin999]

Right, see what you mean - give me a couple of days and I'll have a look ...

M

 

[Martin999]

I presume you cannot mount lvol1 ???

Has anything happened to the system recently, and lvol work etc ...

Any data in lvol1 ???

Ta

 

[Martin999]

OK, sorted I think ...

Looks like the group and lvol1 files have been recovered from an old backup ...

cr--r--r-- 1 root sys 64 0x010000 Jun 25 2004 group
br--r----- 1 root sys 64 0x010001 Jun 25 2004 lvol1
br--r----- 1 root sys 64 0x010005 Jul 23 2005 man0
br--r----- 1 root sys 64 0x010001 Jul 23 2005 man1
br--r----- 1 root sys 64 0x010006 Jul 23 2005 man3
br--r----- 1 root sys 64 0x010004 Jul 23 2005 mantemp
cr--r----- 1 root sys 64 0x010001 Jun 25 2004 rlvol1
cr--r----- 1 root sys 64 0x010005 Jul 23 2005 rman0
cr--r----- 1 root sys 64 0x010001 Jul 23 2005 rman1
cr--r----- 1 root sys 64 0x010006 Jul 23 2005 rman3

Is this a possible cause ???

To fix, try deleting the lvol1 and rlvol1 files, ONLY if, the reason I have suggested could be true.


2nd method to fix, try a vgcfgrestore ...
3rd method ... export / import VG
4th method, blow away, recreate and restore from backup.

These are steps that I would consider, get back to me if you wnt more help.

Martin