[linux-lvm] missing vg after reboot

[linux-lvm] missing vg after reboot

[Michael]

Hi!

I'm using LVM 0.9.1_beta7 on SuSE Linux 7.2.

I created a second VG (the other VG is detected by
vgscan on bootup) with only one PV and added some LV
to it. Later I added a second PV to the second VG and
i copied the old LV to new LV with stripes=2. All this
configuration was made with the lvm tool included in
yast from SuSE.
During reboot the system finds the first VG, but not
the second one, which was detected before, when only
one PV was assigned to it. I was using the second VG
before reboot with two assigned PV. 


*** output, which might be of interest:

server1:/etc/lvmconf # pvdata /dev/hda2
--- Physical volume ---
PV Name               /dev/hda2
VG Name              
��������������������������������������������������������������������
�����������������������npuspupupupupupupupupspupspspspspssp��������㝨����������ppppupupupu
pupupuspupupupupspspupupupspupspupupunP2?PPPPPnrpppp�}��������������������������������������
PV Size               923.51 GB / NOT usable 720.86 GB
[LVM: 586.02 MB]
PV#                   4057395697
PV Status             available
Allocatable           NO
Cur LV                1886614896
PE Size (KByte)       985249850
Total PE              1936748912
Free PE               50003456
Allocated PE          1886745456
PV UUID              
,1HVA7-GV��-H�G>-H,HA-GH71-�H��-OIKOKO

pvdata -- can't seek to volume group struct physical
volume "/dev/hda2"

*** hda2 is the partition, i added later to the second
vg

server1:~ # pvscan /dev/hda2
pvscan -- reading all physical volumes (this may take
a while...)
pvscan -- ACTIVE   PV "/dev/sda2" of VG "system" [3.84
GB / 0 free]
pvscan -- ACTIVE   PV "/dev/sdb2" of VG "system" [3.91
GB / 2.49 GB free]
pvscan -- inactive PV "/dev/hdc2"  is associated to an
unknown VG (run vgscan)
pvscan -- total: 3 [36.25 GB] / in use: 3 [36.25 GB] /
in no VG: 0 [0]

server1:/etc/lvmconf # vgscan
vgscan -- reading all physical volumes (this may take
a while...)
vgscan -- found active volume group "system"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d"
successfully created
vgscan -- WARNING: This program does not do a VGDA
backup of your volume group

*** "system" is the first VG, the missing VG was
called "data"

server1:~ # pvdisplay /dev/hda2
pvdisplay -- no physical volume identifier on
"/dev/hda2"

server1:~ # vgcfgrestore -v -n data /dev/hda2
vgcfgrestore -- locking logical volume manager
vgcfgrestore -- restoring volume group "data" from
"/etc/lvmconf/data.conf"
vgcfgrestore -- checking existence of
"/etc/lvmconf/data.conf"
vgcfgrestore -- reading volume group data for "data"
from "/etc/lvmconf/data.con
f"
vgcfgrestore -- reading physical volume data for
"data" from "/etc/lvmconf/data.
conf"
vgcfgrestore -- reading logical volume data for "data"
from "/etc/lvmconf/data.c
onf"
vgcfgrestore -- checking volume group consistency of
"data"
vgcfgrestore -- checking volume group consistency of
"data"
vgcfgrestore -- reading physical volume "/dev/hda2"
vgcfgrestore -- ERROR "pv_read(): PV identifier
invalid" reading physical volume
 "/dev/hda2"


server1:~ # vgcfgrestore -v -ll -n data /dev/hda2
|more
vgcfgrestore -- locking logical volume manager
vgcfgrestore -- restoring volume group "data" from
"/etc/lvmconf/data.conf"
vgcfgrestore -- checking existence of
"/etc/lvmconf/data.conf"
vgcfgrestore -- reading volume group data for "data"
from "/etc/lvmconf/data.con
f"
vgcfgrestore -- reading physical volume data for
"data" from "/etc/lvmconf/data.
conf"
vgcfgrestore -- reading logical volume data for "data"
from "/etc/lvmconf/data.c
onf"
vgcfgrestore -- checking volume group consistency of
"data"
vgcfgrestore -- checking volume group consistency of
"data"
--- Volume group ---
VG Name               data
VG Access             read/write
VG Status             NOT available/resizable
VG #                  1
MAX LV                256
Cur LV                6
Open LV               0
MAX LV Size           255.99 GB
Max PV                256
Cur PV                2
Act PV                2
VG Size               56.11 GB
PE Size               4 MB
Total PE              14364
Alloc PE / Size       12800 / 50 GB
Free  PE / Size       1564 / 6.11 GB
VG UUID              
k6Out8-Mlm6-2vwt-KgX5-uwKl-3M3V-v732Os

--- Logical volume ---

*** [...]

--- Physical volume ---
PV Name               /dev/hdc2
VG Name               data
PV Size               28.5 GB / NOT usable 580 KB
[LVM: 149 KB]
PV#                   1
PV Status             available
Allocatable           yes
Cur LV                6
PE Size (KByte)       4096
Total PE              7295
Free PE               895
Allocated PE          6400
PV UUID              
QC9SlR-9er7-zW6p-MryA-9T2F-MAJN-2g6ClJ

--- Physical volume ---
PV Name               /dev/hda2
VG Name               data
PV Size               27.62 GB / NOT usable 2.48 MB
[LVM: 148 KB]
PV#                   2
PV Status             available
Allocatable           yes
Cur LV                6
PE Size (KByte)       4096
Total PE              7069
Free PE               669
Allocated PE          6400
PV UUID              
e7sX5R-XnTm-keX6-jShf-tTlw-DUP3-mzp4zW



vgcfgrestore -- unlocking logical volume manager


***

Is there any way to fix the PV on hda2? I tried a tool
called uuid_fixer, but i only got the output "Illegal
instruction" back. 

MfG Michael

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

Re: [linux-lvm] missing vg after reboot

[Heinz J . Mauelshagen]

Michael,

the pvdata output below exposes a completely messy PV structure,
which makes me think of 2 possible reasons:

a. /dev/hda2 is not the device you used to create a physical volume

b. something accidentially overwrote /dev/hda2 after the PV creation


If b is true you might still have an actual VGDA backup in /etc/lvmconf/ which
you can use to vgcfgrestore(8) it to /dev/hda2 presumed that /dev/hda2 is
the right device.


Regards,
Heinz    -- The LVM Guy --


On Sun, Sep 09, 2001 at 03:13:42PM -0700, Michael wrote:
> Hi!
> 
> I'm using LVM 0.9.1_beta7 on SuSE Linux 7.2.
> 
> I created a second VG (the other VG is detected by
> vgscan on bootup) with only one PV and added some LV
> to it. Later I added a second PV to the second VG and
> i copied the old LV to new LV with stripes=2. All this
> configuration was made with the lvm tool included in
> yast from SuSE.
> During reboot the system finds the first VG, but not
> the second one, which was detected before, when only
> one PV was assigned to it. I was using the second VG
> before reboot with two assigned PV. 
> 
> 
> *** output, which might be of interest:
> 
> server1:/etc/lvmconf # pvdata /dev/hda2
> --- Physical volume ---
> PV Name               /dev/hda2
> VG Name              
> ???????????????????????????????????????????????????????????????????????
> ????????????????????????npuspupupupupupupupupspupspspspspssp??????????????????????ppppupupupu
> pupupuspupupupupspspupupupspupspupupunP2?PPPPPnrpppp?}???????????????????????????????????????
> PV Size               923.51 GB / NOT usable 720.86 GB
> [LVM: 586.02 MB]
> PV#                   4057395697
> PV Status             available
> Allocatable           NO
> Cur LV                1886614896
> PE Size (KByte)       985249850
> Total PE              1936748912
> Free PE               50003456
> Allocated PE          1886745456
> PV UUID              
> ,1HVA7-GV??-H?G>-H,HA-GH71-?H??-OIKOKO
> 
> pvdata -- can't seek to volume group struct physical
> volume "/dev/hda2"
> 
> *** hda2 is the partition, i added later to the second
> vg
> 
> server1:~ # pvscan /dev/hda2
> pvscan -- reading all physical volumes (this may take
> a while...)
> pvscan -- ACTIVE   PV "/dev/sda2" of VG "system" [3.84
> GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/sdb2" of VG "system" [3.91
> GB / 2.49 GB free]
> pvscan -- inactive PV "/dev/hdc2"  is associated to an
> unknown VG (run vgscan)
> pvscan -- total: 3 [36.25 GB] / in use: 3 [36.25 GB] /
> in no VG: 0 [0]
> 
> server1:/etc/lvmconf # vgscan
> vgscan -- reading all physical volumes (this may take
> a while...)
> vgscan -- found active volume group "system"
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d"
> successfully created
> vgscan -- WARNING: This program does not do a VGDA
> backup of your volume group
> 
> *** "system" is the first VG, the missing VG was
> called "data"
> 
> server1:~ # pvdisplay /dev/hda2
> pvdisplay -- no physical volume identifier on
> "/dev/hda2"
> 
> server1:~ # vgcfgrestore -v -n data /dev/hda2
> vgcfgrestore -- locking logical volume manager
> vgcfgrestore -- restoring volume group "data" from
> "/etc/lvmconf/data.conf"
> vgcfgrestore -- checking existence of
> "/etc/lvmconf/data.conf"
> vgcfgrestore -- reading volume group data for "data"
> from "/etc/lvmconf/data.con
> f"
> vgcfgrestore -- reading physical volume data for
> "data" from "/etc/lvmconf/data.
> conf"
> vgcfgrestore -- reading logical volume data for "data"
> from "/etc/lvmconf/data.c
> onf"
> vgcfgrestore -- checking volume group consistency of
> "data"
> vgcfgrestore -- checking volume group consistency of
> "data"
> vgcfgrestore -- reading physical volume "/dev/hda2"
> vgcfgrestore -- ERROR "pv_read(): PV identifier
> invalid" reading physical volume
>  "/dev/hda2"
> 
> 
> server1:~ # vgcfgrestore -v -ll -n data /dev/hda2
> |more
> vgcfgrestore -- locking logical volume manager
> vgcfgrestore -- restoring volume group "data" from
> "/etc/lvmconf/data.conf"
> vgcfgrestore -- checking existence of
> "/etc/lvmconf/data.conf"
> vgcfgrestore -- reading volume group data for "data"
> from "/etc/lvmconf/data.con
> f"
> vgcfgrestore -- reading physical volume data for
> "data" from "/etc/lvmconf/data.
> conf"
> vgcfgrestore -- reading logical volume data for "data"
> from "/etc/lvmconf/data.c
> onf"
> vgcfgrestore -- checking volume group consistency of
> "data"
> vgcfgrestore -- checking volume group consistency of
> "data"
> --- Volume group ---
> VG Name               data
> VG Access             read/write
> VG Status             NOT available/resizable
> VG #                  1
> MAX LV                256
> Cur LV                6
> Open LV               0
> MAX LV Size           255.99 GB
> Max PV                256
> Cur PV                2
> Act PV                2
> VG Size               56.11 GB
> PE Size               4 MB
> Total PE              14364
> Alloc PE / Size       12800 / 50 GB
> Free  PE / Size       1564 / 6.11 GB
> VG UUID              
> k6Out8-Mlm6-2vwt-KgX5-uwKl-3M3V-v732Os
> 
> --- Logical volume ---
> 
> *** [...]
> 
> --- Physical volume ---
> PV Name               /dev/hdc2
> VG Name               data
> PV Size               28.5 GB / NOT usable 580 KB
> [LVM: 149 KB]
> PV#                   1
> PV Status             available
> Allocatable           yes
> Cur LV                6
> PE Size (KByte)       4096
> Total PE              7295
> Free PE               895
> Allocated PE          6400
> PV UUID              
> QC9SlR-9er7-zW6p-MryA-9T2F-MAJN-2g6ClJ
> 
> --- Physical volume ---
> PV Name               /dev/hda2
> VG Name               data
> PV Size               27.62 GB / NOT usable 2.48 MB
> [LVM: 148 KB]
> PV#                   2
> PV Status             available
> Allocatable           yes
> Cur LV                6
> PE Size (KByte)       4096
> Total PE              7069
> Free PE               669
> Allocated PE          6400
> PV UUID              
> e7sX5R-XnTm-keX6-jShf-tTlw-DUP3-mzp4zW
> 
> 
> 
> vgcfgrestore -- unlocking logical volume manager
> 
> 
> ***
> 
> Is there any way to fix the PV on hda2? I tried a tool
> called uuid_fixer, but i only got the output "Illegal
> instruction" back. 
> 
> MfG Michael
> 
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
> http://im.yahoo.com
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] missing vg after reboot

[Michael Holschbach]

--- "Heinz J . Mauelshagen" <mauelshagen@sistina.com> wrote:
> 
> Michael,
> 
> the pvdata output below exposes a completely messy PV structure,
> which makes me think of 2 possible reasons:
> 
> a. /dev/hda2 is not the device you used to create a physical volume
> 
> b. something accidentially overwrote /dev/hda2 after the PV creation
> 
> 
> If b is true you might still have an actual VGDA backup in
> /etc/lvmconf/ which
> you can use to vgcfgrestore(8) it to /dev/hda2 presumed that
> /dev/hda2 is
> the right device.
> 
I already tried vgcfgrestore. All available backup files lead to the
same result:
 
> > server1:~ # vgcfgrestore -v -n data /dev/hda2
> > vgcfgrestore -- locking logical volume manager
> > vgcfgrestore -- restoring volume group "data" from
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- checking existence of
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- reading volume group data for "data"
> > from "/etc/lvmconf/data.con
> > f"
> > vgcfgrestore -- reading physical volume data for
> > "data" from "/etc/lvmconf/data.
> > conf"
> > vgcfgrestore -- reading logical volume data for "data"
> > from "/etc/lvmconf/data.c
> > onf"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- reading physical volume "/dev/hda2"
> > vgcfgrestore -- ERROR "pv_read(): PV identifier
> > invalid" reading physical volume
> >  "/dev/hda2"
> > 
My idea was to reset the values of /dev/hda2 according to the following
settings:

> > server1:~ # vgcfgrestore -v -ll -n data /dev/hda2
...
> > --- Physical volume ---
> > PV Name               /dev/hda2
> > VG Name               data
> > PV Size               27.62 GB / NOT usable 2.48 MB
> > [LVM: 148 KB]
> > PV#                   2
> > PV Status             available
> > Allocatable           yes
> > Cur LV                6
> > PE Size (KByte)       4096
> > Total PE              7069
> > Free PE               669
> > Allocated PE          6400
> > PV UUID              
> > e7sX5R-XnTm-keX6-jShf-tTlw-DUP3-mzp4zW
> > 

These values seem plausible for me. Can i use them to manually edit the
PV /dev/hda2 to rescue some data? 


MfG Michael

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

RE: [linux-lvm] missing vg after reboot

[IT3 Stuart B. Tener, USNR-R]

List members:

	It might be worth adding to the How-To that no initscript modifications are necessary for Linux Mandrake, as their default rc.sysinit script contains code in it to do the vg initialization on boot up.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Monday, September 10, 2001 7:34 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Michael Holschbach
Sent: Monday, September 10, 2001 8:49 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] missing vg after reboot


--- "Heinz J . Mauelshagen" <mauelshagen@sistina.com> wrote:
>
> Michael,
>
> the pvdata output below exposes a completely messy PV structure,
> which makes me think of 2 possible reasons:
>
> a. /dev/hda2 is not the device you used to create a physical volume
>
> b. something accidentially overwrote /dev/hda2 after the PV creation
>
>
> If b is true you might still have an actual VGDA backup in
> /etc/lvmconf/ which
> you can use to vgcfgrestore(8) it to /dev/hda2 presumed that
> /dev/hda2 is
> the right device.
>
I already tried vgcfgrestore. All available backup files lead to the
same result:

> > server1:~ # vgcfgrestore -v -n data /dev/hda2
> > vgcfgrestore -- locking logical volume manager
> > vgcfgrestore -- restoring volume group "data" from
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- checking existence of
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- reading volume group data for "data"
> > from "/etc/lvmconf/data.con
> > f"
> > vgcfgrestore -- reading physical volume data for
> > "data" from "/etc/lvmconf/data.
> > conf"
> > vgcfgrestore -- reading logical volume data for "data"
> > from "/etc/lvmconf/data.c
> > onf"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- reading physical volume "/dev/hda2"
> > vgcfgrestore -- ERROR "pv_read(): PV identifier
> > invalid" reading physical volume
> >  "/dev/hda2"
> >
My idea was to reset the values of /dev/hda2 according to the following
settings:

> > server1:~ # vgcfgrestore -v -ll -n data /dev/hda2
...
> > --- Physical volume ---
> > PV Name               /dev/hda2
> > VG Name               data
> > PV Size               27.62 GB / NOT usable 2.48 MB
> > [LVM: 148 KB]
> > PV#                   2
> > PV Status             available
> > Allocatable           yes
> > Cur LV                6
> > PE Size (KByte)       4096
> > Total PE              7069
> > Free PE               669
> > Allocated PE          6400
> > PV UUID             
> > e7sX5R-XnTm-keX6-jShf-tTlw-DUP3-mzp4zW
> >

These values seem plausible for me. Can i use them to manually edit the
PV /dev/hda2 to rescue some data?


MfG Michael

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

RE: [linux-lvm] missing vg after reboot

[Erick Calder]

actually that's also true of RedHat 7.0 and 7.1

- e r i c k

-----Original Message-----
From:	linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com] On
Behalf Of IT3 Stuart B. Tener, USNR-R
Sent:	Monday, September 10, 2001 7:38 PM
To:	linux-lvm@sistina.com
Subject:	RE: [linux-lvm] missing vg after reboot

List members:

	It might be worth adding to the How-To that no initscript modifications are
necessary for Linux Mandrake, as their default rc.sysinit script contains
code in it to do the vg initialization on boot up.


Very Respectfully,

Stuart Blake Tener, IT3, USNR-R, N3GWG
Beverly Hills, California
VTU 1904G (Volunteer Training Unit)
stuart@bh90210.net
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's
free!)

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.

Monday, September 10, 2001 7:34 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On
Behalf Of Michael Holschbach
Sent: Monday, September 10, 2001 8:49 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] missing vg after reboot


--- "Heinz J . Mauelshagen" <mauelshagen@sistina.com> wrote:
>
> Michael,
>
> the pvdata output below exposes a completely messy PV structure,
> which makes me think of 2 possible reasons:
>
> a. /dev/hda2 is not the device you used to create a physical volume
>
> b. something accidentially overwrote /dev/hda2 after the PV creation
>
>
> If b is true you might still have an actual VGDA backup in
> /etc/lvmconf/ which
> you can use to vgcfgrestore(8) it to /dev/hda2 presumed that
> /dev/hda2 is
> the right device.
>
I already tried vgcfgrestore. All available backup files lead to the
same result:

> > server1:~ # vgcfgrestore -v -n data /dev/hda2
> > vgcfgrestore -- locking logical volume manager
> > vgcfgrestore -- restoring volume group "data" from
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- checking existence of
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- reading volume group data for "data"
> > from "/etc/lvmconf/data.con
> > f"
> > vgcfgrestore -- reading physical volume data for
> > "data" from "/etc/lvmconf/data.
> > conf"
> > vgcfgrestore -- reading logical volume data for "data"
> > from "/etc/lvmconf/data.c
> > onf"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- reading physical volume "/dev/hda2"
> > vgcfgrestore -- ERROR "pv_read(): PV identifier
> > invalid" reading physical volume
> >  "/dev/hda2"
> >
My idea was to reset the values of /dev/hda2 according to the following
settings:

> > server1:~ # vgcfgrestore -v -ll -n data /dev/hda2
...
> > --- Physical volume ---
> > PV Name               /dev/hda2
> > VG Name               data
> > PV Size               27.62 GB / NOT usable 2.48 MB
> > [LVM: 148 KB]
> > PV#                   2
> > PV Status             available
> > Allocatable           yes
> > Cur LV                6
> > PE Size (KByte)       4096
> > Total PE              7069
> > Free PE               669
> > Allocated PE          6400
> > PV UUID
> > e7sX5R-XnTm-keX6-jShf-tTlw-DUP3-mzp4zW
> >

These values seem plausible for me. Can i use them to manually edit the
PV /dev/hda2 to rescue some data?


MfG Michael

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿåŠ{±þ[æ(tm)¨¥Šx%ŠËeŠ{±þ[æþȬ¶)ÚýÊ&†ÛiÿÿåŠ
ËlþȬ¶)ÚýÊ&þf¢-f§þX¬¶)ߣùbžìÿ-ù«y§m...âÕ0s-ý3š¶^[m§ÿÿÃ
ÿ²+-Švÿr‰¿-ù¿=¨-³øhÂÚÿ†Ù¥

RE: [linux-lvm] missing vg after reboot

[IT3 Stuart B. Tener, USNR-R]

Erick:

	That also ought be noted in the how-to.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Monday, September 10, 2001 9:08 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Erick Calder
Sent: Monday, September 10, 2001 8:47 PM
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] missing vg after reboot

actually that's also true of RedHat 7.0 and 7.1

- e r i c k

-----Original Message-----
From:   linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com] On
Behalf Of IT3 Stuart B. Tener, USNR-R
Sent:   Monday, September 10, 2001 7:38 PM
To:     linux-lvm@sistina.com
Subject:        RE: [linux-lvm] missing vg after reboot

List members:

        It might be worth adding to the How-To that no initscript modifications are
necessary for Linux Mandrake, as their default rc.sysinit script contains
code in it to do the vg initialization on boot up.


Very Respectfully,

Stuart Blake Tener, IT3, USNR-R, N3GWG
Beverly Hills, California
VTU 1904G (Volunteer Training Unit)
stuart@bh90210.net
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's
free!)

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.

Monday, September 10, 2001 7:34 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On
Behalf Of Michael Holschbach
Sent: Monday, September 10, 2001 8:49 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] missing vg after reboot


--- "Heinz J . Mauelshagen" <mauelshagen@sistina.com> wrote:
>
> Michael,
>
> the pvdata output below exposes a completely messy PV structure,
> which makes me think of 2 possible reasons:
>
> a. /dev/hda2 is not the device you used to create a physical volume
>
> b. something accidentially overwrote /dev/hda2 after the PV creation
>
>
> If b is true you might still have an actual VGDA backup in
> /etc/lvmconf/ which
> you can use to vgcfgrestore(8) it to /dev/hda2 presumed that
> /dev/hda2 is
> the right device.
>
I already tried vgcfgrestore. All available backup files lead to the
same result:

> > server1:~ # vgcfgrestore -v -n data /dev/hda2
> > vgcfgrestore -- locking logical volume manager
> > vgcfgrestore -- restoring volume group "data" from
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- checking existence of
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- reading volume group data for "data"
> > from "/etc/lvmconf/data.con
> > f"
> > vgcfgrestore -- reading physical volume data for
> > "data" from "/etc/lvmconf/data.
> > conf"
> > vgcfgrestore -- reading logical volume data for "data"
> > from "/etc/lvmconf/data.c
> > onf"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- reading physical volume "/dev/hda2"
> > vgcfgrestore -- ERROR "pv_read(): PV identifier
> > invalid" reading physical volume
> >  "/dev/hda2"
> >
My idea was to reset the values of /dev/hda2 according to the following
settings:

> > server1:~ # vgcfgrestore -v -ll -n data /dev/hda2
...
> > --- Physical volume ---
> > PV Name               /dev/hda2
> > VG Name               data
> > PV Size               27.62 GB / NOT usable 2.48 MB
> > [LVM: 148 KB]
> > PV#                   2
> > PV Status             available
> > Allocatable           yes
> > Cur LV                6
> > PE Size (KByte)       4096
> > Total PE              7069
> > Free PE               669
> > Allocated PE          6400
> > PV UUID
> > e7sX5R-XnTm-keX6-jShf-tTlw-DUP3-mzp4zW
> >

These values seem plausible for me. Can i use them to manually edit the
PV /dev/hda2 to rescue some data?


MfG Michael

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿåŠ{±þ[æ(tm)¨¥Šx%ŠËeŠ{±þ[æþȬ¶)ÚýÊ&†ÛiÿÿåŠ
ËlþȬ¶)ÚýÊ&þf¢-f§þX¬¶)ߣùbžìÿ-ù"y§m...âÕ0s-ý3š¶^[m§ÿÿÃ
ÿ²+-Švÿr‰¿-ù¿=¨-³øhÂÚÿ†Ù¥


_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Re: [linux-lvm] missing vg after reboot

[Glenn Shannon]

And Debian initscripts are taken care of if you "apt-get install lvmtools" I
believe.....I would double check that but I am not *gasp* in Linux right now
:)

Glenn
----- Original Message -----
From: "Erick Calder" <e@arix.com>
To: <linux-lvm@sistina.com>
Sent: Monday, September 10, 2001 8:46 PM
Subject: RE: [linux-lvm] missing vg after reboot


actually that's also true of RedHat 7.0 and 7.1

- e r i c k

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com] On
Behalf Of IT3 Stuart B. Tener, USNR-R
Sent: Monday, September 10, 2001 7:38 PM
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] missing vg after reboot

List members:

It might be worth adding to the How-To that no initscript modifications are
necessary for Linux Mandrake, as their default rc.sysinit script contains
code in it to do the vg initialization on boot up.


Very Respectfully,

Stuart Blake Tener, IT3, USNR-R, N3GWG
Beverly Hills, California
VTU 1904G (Volunteer Training Unit)
stuart@bh90210.net
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's
free!)

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.

Monday, September 10, 2001 7:34 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On
Behalf Of Michael Holschbach
Sent: Monday, September 10, 2001 8:49 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] missing vg after reboot


--- "Heinz J . Mauelshagen" <mauelshagen@sistina.com> wrote:
>
> Michael,
>
> the pvdata output below exposes a completely messy PV structure,
> which makes me think of 2 possible reasons:
>
> a. /dev/hda2 is not the device you used to create a physical volume
>
> b. something accidentially overwrote /dev/hda2 after the PV creation
>
>
> If b is true you might still have an actual VGDA backup in
> /etc/lvmconf/ which
> you can use to vgcfgrestore(8) it to /dev/hda2 presumed that
> /dev/hda2 is
> the right device.
>
I already tried vgcfgrestore. All available backup files lead to the
same result:

> > server1:~ # vgcfgrestore -v -n data /dev/hda2
> > vgcfgrestore -- locking logical volume manager
> > vgcfgrestore -- restoring volume group "data" from
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- checking existence of
> > "/etc/lvmconf/data.conf"
> > vgcfgrestore -- reading volume group data for "data"
> > from "/etc/lvmconf/data.con
> > f"
> > vgcfgrestore -- reading physical volume data for
> > "data" from "/etc/lvmconf/data.
> > conf"
> > vgcfgrestore -- reading logical volume data for "data"
> > from "/etc/lvmconf/data.c
> > onf"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- checking volume group consistency of
> > "data"
> > vgcfgrestore -- reading physical volume "/dev/hda2"
> > vgcfgrestore -- ERROR "pv_read(): PV identifier
> > invalid" reading physical volume
> >  "/dev/hda2"
> >
My idea was to reset the values of /dev/hda2 according to the following
settings:

> > server1:~ # vgcfgrestore -v -ll -n data /dev/hda2
...
> > --- Physical volume ---
> > PV Name               /dev/hda2
> > VG Name               data
> > PV Size               27.62 GB / NOT usable 2.48 MB
> > [LVM: 148 KB]
> > PV#                   2
> > PV Status             available
> > Allocatable           yes
> > Cur LV                6
> > PE Size (KByte)       4096
> > Total PE              7069
> > Free PE               669
> > Allocated PE          6400
> > PV UUID
> > e7sX5R-XnTm-keX6-jShf-tTlw-DUP3-mzp4zW
> >

These values seem plausible for me. Can i use them to manually edit the
PV /dev/hda2 to rescue some data?


MfG Michael

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿåS{±þ[æ(tm)¨¥Sx%SËeS{±þ[æþȬ¶)ÚýÊ&?ÛiÿÿåS
ËlþȬ¶)ÚýÊ&þf¢-f§þX¬¶)ߣùbzìÿ-ù«y§m...âÕ0s-ý3s¶^[m§ÿÿÃ
ÿ²+-Svÿr?¿-ù¿=¨-³øhÂÚÿ?Ù¥


_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Re: [linux-lvm] missing vg after reboot

[Heinz J . Mauelshagen]

vgcfgrestore only works on a new PV.
Run "pvcreate -ff /dev/YourDevice" *before trying vgcfgrestore on it.

Regards,
Heinz    -- The LVM Guy --

On Mon, Sep 10, 2001 at 08:49:03AM -0700, Michael Holschbach wrote:
> 
> --- "Heinz J . Mauelshagen" <mauelshagen@sistina.com> wrote:
> > 
> > Michael,
> > 
> > the pvdata output below exposes a completely messy PV structure,
> > which makes me think of 2 possible reasons:
> > 
> > a. /dev/hda2 is not the device you used to create a physical volume
> > 
> > b. something accidentially overwrote /dev/hda2 after the PV creation
> > 
> > 
> > If b is true you might still have an actual VGDA backup in
> > /etc/lvmconf/ which
> > you can use to vgcfgrestore(8) it to /dev/hda2 presumed that
> > /dev/hda2 is
> > the right device.
> > 
> I already tried vgcfgrestore. All available backup files lead to the
> same result:
>  
> > > server1:~ # vgcfgrestore -v -n data /dev/hda2
> > > vgcfgrestore -- locking logical volume manager
> > > vgcfgrestore -- restoring volume group "data" from
> > > "/etc/lvmconf/data.conf"
> > > vgcfgrestore -- checking existence of
> > > "/etc/lvmconf/data.conf"
> > > vgcfgrestore -- reading volume group data for "data"
> > > from "/etc/lvmconf/data.con
> > > f"
> > > vgcfgrestore -- reading physical volume data for
> > > "data" from "/etc/lvmconf/data.
> > > conf"
> > > vgcfgrestore -- reading logical volume data for "data"
> > > from "/etc/lvmconf/data.c
> > > onf"
> > > vgcfgrestore -- checking volume group consistency of
> > > "data"
> > > vgcfgrestore -- checking volume group consistency of
> > > "data"
> > > vgcfgrestore -- reading physical volume "/dev/hda2"
> > > vgcfgrestore -- ERROR "pv_read(): PV identifier
> > > invalid" reading physical volume
> > >  "/dev/hda2"
> > > 
> My idea was to reset the values of /dev/hda2 according to the following
> settings:
> 
> > > server1:~ # vgcfgrestore -v -ll -n data /dev/hda2
> ...
> > > --- Physical volume ---
> > > PV Name               /dev/hda2
> > > VG Name               data
> > > PV Size               27.62 GB / NOT usable 2.48 MB
> > > [LVM: 148 KB]
> > > PV#                   2
> > > PV Status             available
> > > Allocatable           yes
> > > Cur LV                6
> > > PE Size (KByte)       4096
> > > Total PE              7069
> > > Free PE               669
> > > Allocated PE          6400
> > > PV UUID              
> > > e7sX5R-XnTm-keX6-jShf-tTlw-DUP3-mzp4zW
> > > 
> 
> These values seem plausible for me. Can i use them to manually edit the
> PV /dev/hda2 to rescue some data? 
> 
> 
> MfG Michael
> 
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
> http://im.yahoo.com
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-