[linux-lvm] Missing (or double) logical volume after upgrade to 2.4.7 and beta8

[linux-lvm] Missing (or double) logical volume after upgrade to 2.4.7 and beta8

[Melis van den Brink]

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

Hello,

I'm experiencing a bit of trouble with LVM (just as I was becoming very happy 
with it :-().
I had it running on a 2.4.6 kernel patched with the beta7 lvm-stuff and some 
patches from the reiserfs-guys. That was running quite fine.
Today I performed the upgrade to linux 2.4.7 and lvm beta8. I followed the 
advice from the README.1st in upgrading to the new meta-format. I installed 
the beta8 tools and booted with the new kernel (including the patches from 
beta8). It seemed to be working until I discovered that one of my LV's was 
missing. Or better it showed the same filesystem as the one mounted on /var.

I could try to fix it, but would like to know some options as I am fairly new 
to LVM.
Attached is some information about the LVM-setup. I can give you some more, 
but I don't know what to provide you with...

[-- Attachment #2: lvm.pr.txt --]
[-- Type: text/plain, Size: 2699 bytes --]


pvscan: Logical Volume Manager 0.9.1_beta8
Heinz Mauelshagen, Sistina Software  24/07/2001 (IOP 10)

pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/sda1" of VG "vg_vmware" [1.95 GB / 0 free]
pvscan -- inactive PV "/dev/sdb1" of VG "vg_ibm"    [2.00 GB / 44.00 MB free]
pvscan -- ACTIVE   PV "/dev/hdc4" of VG "vg_root"   [7.17 GB / 2.55 GB free]
pvscan -- ACTIVE   PV "/dev/hdc6" of VG "vg_root"   [1.52 GB / 0 free]
pvscan -- total: 4 [12.64 GB] / in use: 4 [12.64 GB] / in no VG: 0 [0]

lvscan -- checking volume group name "vg_ibm"
lvscan -- checking volume group "vg_ibm" existence
lvscan -- checking volume group "vg_ibm" activity
lvscan -- volume group "vg_ibm" is NOT active; try -D
lvscan -- checking volume group name "vg_root"
lvscan -- checking volume group "vg_root" existence
lvscan -- checking volume group "vg_root" activity
lvscan -- getting VGDA of volume group "vg_root" from kernel
lvscan -- ACTIVE            "/dev/vg_root/lv_var" [652.00 MB]
lvscan -- ACTIVE            "/dev/vg_root/lv_opt" [2.50 GB]
lvscan -- ACTIVE            "/dev/vg_root/lv_home" [1.00 GB]
lvscan -- ACTIVE            "/dev/vg_root/lv_usr" [2.00 GB]
lvscan -- checking volume group name "vg_vmware"
lvscan -- checking volume group "vg_vmware" existence
lvscan -- checking volume group "vg_vmware" activity
lvscan -- getting VGDA of volume group "vg_vmware" from kernel
lvscan -- ACTIVE            "/dev/vg_root/lv_var" [652.00 MB]
lvscan -- ACTIVE            "/dev/vg_root/lv_opt" [2.50 GB]
lvscan -- ACTIVE            "/dev/vg_root/lv_home" [1.00 GB]
lvscan -- ACTIVE            "/dev/vg_root/lv_usr" [2.00 GB]
lvscan -- 8 logical volumes with 12.27 GB total in 2 volume groups
lvscan -- 8 active logical volumes

#
# @(#)fstab - A listing of all the devices waiting to be mounted.
#
# History:
# 27-Jul-2001 (brinm00):
#	Added the comments.
#
#Device			Mnt-point	Type	Options
#-------------------------------------------------------------------------------
none			/proc		proc	defaults							0 0
none			/dev/pts	devpts	mode=0620 0 0

/dev/hdc2		swap		swap	defaults							0 0
/dev/hdc3		/		ext2	exec,dev,suid,rw,usrquota,grpquota	1 1

/dev/vg_root/lv_usr	/usr		reiserfs	defaults						1 3
/dev/vg_root/lv_var	/var		reiserfs	defaults						1 3
/dev/vg_root/lv_home	/home		reiserfs	defaults						1 3
/dev/vg_root/lv_opt	/opt		reiserfs	defaults						1 3

#/dev/vg_vmware/lv_vmware	/mnt/vmware		reiserfs	defaults						1 3

/dev/sr0		/mnt/cdrom	iso9660	ro,nosuid,noauto,exec,user,nodev	0 0
/dev/fd0		/mnt/floppy	vfat	sync,nosuid,noauto,user,nodev,unhide	0 0
#/dev/hda1	/mnt/win_c	vfat	user,exec,umask=0					0 0
#/dev/hdc5	/mnt/games	vfat	user,exec,umask=0					0 0

[linux-lvm] LVM / RAID MIB for SNMP

[Arvind Jain]

Does anyone know if there is MIB available for LVM / RAID  for SNMP management?
thx, arvind.

Re: [linux-lvm] Missing (or double) logical volume after upgrade to 2.4.7 and beta8

[Patrick Caulfield]

On Mon, Aug 06, 2001 at 09:06:01PM +0200, Melis van den Brink wrote:
> Hello,
> 
> I'm experiencing a bit of trouble with LVM (just as I was becoming very happy 
> with it :-().
> I had it running on a 2.4.6 kernel patched with the beta7 lvm-stuff and some 
> patches from the reiserfs-guys. That was running quite fine.
> Today I performed the upgrade to linux 2.4.7 and lvm beta8. I followed the 
> advice from the README.1st in upgrading to the new meta-format. I installed 
> the beta8 tools and booted with the new kernel (including the patches from 
> beta8). It seemed to be working until I discovered that one of my LV's was 
> missing. Or better it showed the same filesystem as the one mounted on /var.
> 
> I could try to fix it, but would like to know some options as I am fairly new 
> to LVM.
> Attached is some information about the LVM-setup. I can give you some more, 
> but I don't know what to provide you with...

At a guess it sounds like one (or more) of the PVs hasn't had it's metadat
version number updated - there are several inactive PVs shown by PVSCAN. Check
that all your PVs are shown there (if not then get the beta6 tools and run
pvversion on them) and then run vgscan.

The "duplicate" volume is probably just an old volume not being activated and
it's major/minor number being reused by another volume that has been activated.
"ls -l" on the names will show this. If you're worried about it then just delete
the incorrect device nodes. Once all the VGs are activated they should sort
themselves out.

patrick

Re: [linux-lvm] Missing (or double) logical volume after upgrade to 2.4.7 and beta8

[Melis van den Brink]

On Tuesday 07 August 2001 09:24, you wrote:
> On Mon, Aug 06, 2001 at 09:06:01PM +0200, Melis van den Brink wrote:
> > Hello,
> >
> > I'm experiencing a bit of trouble with LVM (just as I was becoming very
> > happy with it :-().
> > I had it running on a 2.4.6 kernel patched with the beta7 lvm-stuff and
> > some patches from the reiserfs-guys. That was running quite fine.
> > Today I performed the upgrade to linux 2.4.7 and lvm beta8. I followed
> > the advice from the README.1st in upgrading to the new meta-format. I
> > installed the beta8 tools and booted with the new kernel (including the
> > patches from beta8). It seemed to be working until I discovered that one
> > of my LV's was missing. Or better it showed the same filesystem as the
> > one mounted on /var.
> >
> > I could try to fix it, but would like to know some options as I am fairly
> > new to LVM.
> > Attached is some information about the LVM-setup. I can give you some
> > more, but I don't know what to provide you with...
>
> At a guess it sounds like one (or more) of the PVs hasn't had it's metadat
> version number updated - there are several inactive PVs shown by PVSCAN.
> Check that all your PVs are shown there (if not then get the beta6 tools
> and run pvversion on them) and then run vgscan.
Do you mean the beta8 tools (meaning '6' is just a typo) or is there a reason 
for pointing to the beta6 tools ?

>
> The "duplicate" volume is probably just an old volume not being activated
> and it's major/minor number being reused by another volume that has been
> activated. "ls -l" on the names will show this. If you're worried about it
> then just delete the incorrect device nodes. Once all the VGs are activated
> they should sort themselves out.
>

Melis

Re: [linux-lvm] Missing (or double) logical volume after upgrade to 2.4.7 and beta8

[Patrick Caulfield]

On Tue, Aug 07, 2001 at 07:19:21PM +0200, Melis van den Brink wrote:
> >
> > At a guess it sounds like one (or more) of the PVs hasn't had it's metadat
> > version number updated - there are several inactive PVs shown by PVSCAN.
> > Check that all your PVs are shown there (if not then get the beta6 tools
> > and run pvversion on them) and then run vgscan.

> Do you mean the beta8 tools (meaning '6' is just a typo) or is there a reason 
> for pointing to the beta6 tools ?

No, you'll need the tools that match those that created them. So the beta8 tools
won't see the old PVs but beta6 should. 6 is good number! 



patrick

Re: [linux-lvm] Missing (or double) logical volume after upgrade to 2.4.7 and beta8 (follow-up)

[Melis van den Brink]

On Monday 06 August 2001 21:06, you wrote:
> Hello,
>
> I'm experiencing a bit of trouble with LVM (just as I was becoming very
> happy with it :-().
> I had it running on a 2.4.6 kernel patched with the beta7 lvm-stuff and
> some patches from the reiserfs-guys. That was running quite fine.
> Today I performed the upgrade to linux 2.4.7 and lvm beta8. I followed the
> advice from the README.1st in upgrading to the new meta-format. I installed
> the beta8 tools and booted with the new kernel (including the patches from
> beta8). It seemed to be working until I discovered that one of my LV's was
> missing. Or better it showed the same filesystem as the one mounted on
> /var.
>
> I could try to fix it, but would like to know some options as I am fairly
> new to LVM.
> Attached is some information about the LVM-setup. I can give you some more,
> but I don't know what to provide you with...

OK,

The problem seems fixed (or at-least worked around): this particular LV/VG is 
on a SCSI-disk. The SCSI-subsystem as well as the SCSI-driver (aic7xxx.o) 
were loadable modules. Today I made a new kernel with these parts no longer 
as a module but in the kernel itself. The result: at boot/initialisation time 
the SCSI-system gets loaded, the SCSI-drives get their initialisation and LVM 
when "vgscan"-ing or "vgchange"-ing sees all the volumes.
Weird as it is: at the moment this doesn't work when the SCSI-stuff is 
compiled as a loadable module. Any suggestions: some change in the init-stuff 
(it's on a 7.2 Mandrake system) or is my current setup the only way to go.

Melis

Re: [linux-lvm] Missing (or double) logical volume after upgrade to 2.4.7 and beta8 (follow-up)

[Patrick Caulfield]

On Tue, Aug 07, 2001 at 08:36:11PM +0200, Melis van den Brink wrote:
> 
> The problem seems fixed (or at-least worked around): this particular LV/VG is 
> on a SCSI-disk. The SCSI-subsystem as well as the SCSI-driver (aic7xxx.o) 
> were loadable modules. Today I made a new kernel with these parts no longer 
> as a module but in the kernel itself. The result: at boot/initialisation time 
> the SCSI-system gets loaded, the SCSI-drives get their initialisation and LVM 
> when "vgscan"-ing or "vgchange"-ing sees all the volumes.
> Weird as it is: at the moment this doesn't work when the SCSI-stuff is 
> compiled as a loadable module. Any suggestions: some change in the init-stuff 
> (it's on a 7.2 Mandrake system) or is my current setup the only way to go.

I would go with whatever works for you! All I can think of is that the SCSI
modules are loaded after vgscan runs. That would explain the output you posted
earlier.

patrick