[linux-lvm] My VG is gone...

[linux-lvm] My VG is gone...

[Rasmus Wiman]

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

...And I want them up quickly!

This evening I added a 36 GB drive to our department server. I did a
vgextend on it and somehow it all went terribly wrong. It seems to me that
the new drive got added twice, but with different UUIDs. Of course there
is no way vgchange will bring it online. Is there a solution to the
problem? I downloaded LDE from <http://lde.sourceforge.net/> to have a
look at it, but I don't know what to alter. I run Slackware 8 with Kernel
2.4.8 and LVM-1.0. The attached files contain output from pvdata -U -V -PP
on all three partitions.

Thanks in advance,


Rasmus Wiman
SAMI Labs

[-- Attachment #2: sda2.txt --]
[-- Type: application/octet-stream, Size: 1575 bytes --]

--- Physical volume ---
PV Name               /dev/sda2
VG Name               vg1
PV Size               3.73 GB / NOT usable 7.00 MB [LVM: 127.00 KB]
PV#                   1
PV Status             available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       4096
Total PE              952
Free PE               0
Allocated PE          952
PV UUID               7NM68S-YjOx-J8Pr-URMO-2hdo-2Kkh-0gn1g4
pv_dev                   0:8
system_id                labrat997907659
pv_on_disk.base          0
pv_on_disk.size          1024
vg_on_disk.base          4096
vg_on_disk.size          4096
pv_uuidlist_on_disk.base 8192
pv_uuidlist_on_disk.size 32768
lv_on_disk.base          40960
lv_on_disk.size          83968
pe_on_disk.base          126976
pe_on_disk.size          65536


--- Volume group ---
VG Name               
VG Access             read/write
VG Status             NOT available/resizable
VG #                  0
MAX LV                255
Cur LV                2
Open LV               0
MAX LV Size           255.99 GB
Max PV                255
Cur PV                4
Act PV                4
VG Size               76.82 GB
PE Size               4.00 MB
Total PE              19667
Alloc PE / Size       2169 / 8.47 GB
Free  PE / Size       17498 / 68.35 GB
VG UUID               ma2VsH-ZSVm-v9Jj-PW2x-mk4b-udtz-L16nwI
--- List of physical volume UUIDs ---

001: 7NM68S-YjOx-J8Pr-URMO-2hdo-2Kkh-0gn1g4
002: x2jjry-WEho-sJmp-PLVM-5m5S-hwGs-0C1PC0
003: 6XdTr0-2PF0-sPrp-d9qx-Xdw2-1wNb-XUpWpW
004: 2E2mM4-CiqB-BlwG-j6ZW-CPfB-z9kz-sd7VAD


[-- Attachment #3: sda3.txt --]
[-- Type: application/octet-stream, Size: 1577 bytes --]

--- Physical volume ---
PV Name               /dev/sda3
VG Name               vg1
PV Size               4.76 GB / NOT usable 8.00 MB [LVM: 128.00 KB]
PV#                   2
PV Status             available
Allocatable           yes (but full)
Cur LV                2
PE Size (KByte)       4096
Total PE              1217
Free PE               0
Allocated PE          1217
PV UUID               x2jjry-WEho-sJmp-PLVM-5m5S-hwGs-0C1PC0
pv_dev                   0:8
system_id                labrat997912217
pv_on_disk.base          0
pv_on_disk.size          1024
vg_on_disk.base          4096
vg_on_disk.size          4096
pv_uuidlist_on_disk.base 8192
pv_uuidlist_on_disk.size 32768
lv_on_disk.base          40960
lv_on_disk.size          83968
pe_on_disk.base          126976
pe_on_disk.size          65536


--- Volume group ---
VG Name               
VG Access             read/write
VG Status             NOT available/resizable
VG #                  0
MAX LV                255
Cur LV                2
Open LV               0
MAX LV Size           255.99 GB
Max PV                255
Cur PV                4
Act PV                4
VG Size               76.82 GB
PE Size               4.00 MB
Total PE              19667
Alloc PE / Size       2169 / 8.47 GB
Free  PE / Size       17498 / 68.35 GB
VG UUID               ma2VsH-ZSVm-v9Jj-PW2x-mk4b-udtz-L16nwI
--- List of physical volume UUIDs ---

001: 7NM68S-YjOx-J8Pr-URMO-2hdo-2Kkh-0gn1g4
002: x2jjry-WEho-sJmp-PLVM-5m5S-hwGs-0C1PC0
003: 6XdTr0-2PF0-sPrp-d9qx-Xdw2-1wNb-XUpWpW
004: 2E2mM4-CiqB-BlwG-j6ZW-CPfB-z9kz-sd7VAD


[-- Attachment #4: sdb1.txt --]
[-- Type: application/octet-stream, Size: 1574 bytes --]

--- Physical volume ---
PV Name               /dev/sdb1
VG Name               vg1
PV Size               34.18 GB / NOT usable 7.00 MB [LVM: 158.00 KB]
PV#                   4
PV Status             NOT available
Allocatable           yes
Cur LV                0
PE Size (KByte)       4096
Total PE              8749
Free PE               8749
Allocated PE          0
PV UUID               2E2mM4-CiqB-BlwG-j6ZW-CPfB-z9kz-sd7VAD
pv_dev                   0:8
system_id                slackware999219197
pv_on_disk.base          0
pv_on_disk.size          1024
vg_on_disk.base          4096
vg_on_disk.size          4096
pv_uuidlist_on_disk.base 8192
pv_uuidlist_on_disk.size 32768
lv_on_disk.base          40960
lv_on_disk.size          83968
pe_on_disk.base          126976
pe_on_disk.size          65536


--- Volume group ---
VG Name               
VG Access             read/write
VG Status             NOT available/resizable
VG #                  0
MAX LV                255
Cur LV                2
Open LV               0
MAX LV Size           255.99 GB
Max PV                255
Cur PV                4
Act PV                4
VG Size               76.82 GB
PE Size               4.00 MB
Total PE              19667
Alloc PE / Size       2169 / 8.47 GB
Free  PE / Size       17498 / 68.35 GB
VG UUID               ma2VsH-ZSVm-v9Jj-PW2x-mk4b-udtz-L16nwI
--- List of physical volume UUIDs ---

001: 7NM68S-YjOx-J8Pr-URMO-2hdo-2Kkh-0gn1g4
002: x2jjry-WEho-sJmp-PLVM-5m5S-hwGs-0C1PC0
003: 6XdTr0-2PF0-sPrp-d9qx-Xdw2-1wNb-XUpWpW
004: 2E2mM4-CiqB-BlwG-j6ZW-CPfB-z9kz-sd7VAD

Re: [linux-lvm] My VG is gone...

[Rasmus Wiman]

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


> ...And I want them up quickly!

I thought I'd add some vgdisplay output too, here it is, taken with
vgdisplay -d.


---------------------
Rasmus Wiman
SAMI Labs

[-- Attachment #2: vgdisplay.txt --]
[-- Type: application/octet-stream, Size: 890 bytes --]

<1> lvm_check_kernel_lvmtab_consistency -- CALLED
<22> vg_check_active_all_vg -- CALLED
<333> vg_status_get_count -- CALLED
<333> vg_status_get_count -- LEAVING with ret: 0
<22> vg_check_active_all_vg -- LEAVING with ret: -331  ptr: (null)
<22> lvm_tab_vg_check_exist_all_vg -- CALLED
<333> lvm_tab_read -- CALLED
<333> lvm_tab_read -- LEAVING with ret: 0  data: 804B588  size: 1
<22> lvm_tab_vg_check_exist_all_vg -- LEAVING with ret: 0
<1> lvm_check_kernel_lvmtab_consistency -- LEAVING with ret: 1
<1> lvm_get_iop_version -- CALLED
<22> lvm_check_special -- CALLED
<22> lvm_check_special -- LEAVING
<1> lvm_get_iop_version -- AFTER ioctl ret: 0
<1> lvm_get_iop_version -- LEAVING with ret: 10
<1> lvm_tab_vg_check_exist_all_vg -- CALLED
<22> lvm_tab_read -- CALLED
<22> lvm_tab_read -- LEAVING with ret: 0  data: 804B588  size: 1
<1> lvm_tab_vg_check_exist_all_vg -- LEAVING with ret: 0

Re: [linux-lvm] My VG is gone...

[Joe Thornber]

On Fri, Aug 31, 2001 at 07:15:18AM +0200, Rasmus Wiman wrote:
> ...And I want them up quickly!
> 
> This evening I added a 36 GB drive to our department server. I did a
> vgextend on it and somehow it all went terribly wrong. It seems to me that
> the new drive got added twice, but with different UUIDs. Of course there
> is no way vgchange will bring it online. Is there a solution to the
> problem? I downloaded LDE from <http://lde.sourceforge.net/> to have a
> look at it, but I don't know what to alter. I run Slackware 8 with Kernel
> 2.4.8 and LVM-1.0. The attached files contain output from pvdata -U -V -PP
> on all three partitions.

You're right sdb1 appears to have been added twice with seperate
UUID's.  I'm at a loss to explain this at the moment.  Did you run
pvcreate more than once on sdb1 ? (I want to know where that extra
uuid came from).

- Joe

Re: [linux-lvm] My VG is gone...

[Rasmus Wiman]

Joe Thornber <thornber@btconnect.com> skrev:

> > This evening I added a 36 GB drive to our department server. I did a
> > vgextend on it and somehow it all went terribly wrong. It seems to me
> that
> > the new drive got added twice, but with different UUIDs. Of course
> there
> > is no way vgchange will bring it online. Is there a solution to the
> > problem? I downloaded LDE from <http://lde.sourceforge.net/> to have a
> > look at it, but I don't know what to alter. I run Slackware 8 with
> Kernel
> > 2.4.8 and LVM-1.0. The attached files contain output from pvdata -U -V
> -PP
> > on all three partitions.
> 
> You're right sdb1 appears to have been added twice with seperate
> UUID's.  I'm at a loss to explain this at the moment.  Did you run
> pvcreate more than once on sdb1 ? (I want to know where that extra
> uuid came from).

Well here's the full story:
I added the new disk, made a new LVM partition, ran pvcreate on it. Did a
vgextend vg1 /dev/sdb1. Rebooted. No vg:s found, Panic: root not found.
Spent a bunch of hours hackaing a Slackware 8 boot floppy with LVM 1.0
support. It found the vg. Next idea: Maybe it's because of devfs. I hacked
the disk a bit further yo use devfs, and now it didn't find the VG:s. I
started looking for any LVM list archive, found something about small
initrd:s so I put an 8 MB initrd image on the root floppy, and wow, the VG
was there. Tried to put a larger initrd on the boot partition and re-ran
lilo. Rebooted, no success. Later I realised that a initrd_size=8912k
might have done the trick. Booted from the floppy again and did a vgreduce
vg1 /dev/sdb1. Now it would boot. Here I should really have backed up
everything to a non LVM partition, but instead I did a vgextend vg1 sdb1.
Re-ran lvmcreate_initrd, re-ran lilo and rebooted. That's where I am now.
Two SDB1:s with separate UUID's. Can this be fixed or should I format and
reinstall? It would really feel bad because I've never had to format and
reinstall a Linux system except for the occasional hardware failure.


---------------------
Rasmus Wiman
SAMI Labs

Re: [linux-lvm] My VG is gone...

[svetljo]

Hi could you post one more time the
output from pvdata -U -V -PP and vgdisplay -d

maybe inline and not as attachments because my Mozilla treats the 
attachment as plain text the same is with konqueror
i see only smth of the kind :

---------------------
Rasmus Wiman
SAMI Labs

--Multipart_Fri__31_Aug_2001_09:41:46_+0200_08e497f0
Content-Type: application/octet-stream;
 name="vgdisplay.txt"
Content-Disposition: attachment;
 filename="vgdisplay.txt"
Content-Transfer-Encoding: base64

PDE+IGx2bV9jaGVja19rZXJuZWxfbHZtdGFiX2NvbnNpc3RlbmN5IC0tIENBTExFRAo8MjI+IHZn
X2NoZWNrX2FjdGl2ZV9hbGxfdmcgLS0gQ0FMTEVECjwzMzM+IHZnX3N0YXR1c19nZXRfY291bnQg
LS0gQ0FMTEVECjwzMzM+IHZnX3N0YXR1c19nZXRfY291bnQgLS0gTEVBVklORyB3aXRoIHJldDog
MAo8MjI+IHZnX2NoZWNrX2FjdGl2ZV9hbGxfdmcgLS0gTEVBVklORyB3aXRoIHJldDogLTMzMSAg
cHRyOiAobnVsbCkKPDIyPiBsdm1fdGFiX3ZnX2NoZWNrX2V4aXN0X2FsbF92ZyAtLSBDQUxMRUQK
PDMzMz4gbHZtX3RhYl9yZWFkIC0tIENBTExFRAo8MzMzPiBsdm1fdGFiX3JlYWQgLS0gTEVBVklO
RyB3aXRoIHJldDogMCAgZGF0YTogODA0QjU4OCAgc2l6ZTogMQo8MjI+IGx2bV90YWJfdmdfY2hl
Y2tfZXhpc3RfYWxsX3ZnIC0tIExFQVZJTkcgd2l0aCByZXQ6IDAKPDE+IGx2bV9jaGVja19rZXJu
ZWxfbHZtdGFiX2NvbnNpc3RlbmN5IC0tIExFQVZJTkcgd2l0aCByZXQ6IDEKPDE+IGx2bV9nZXRf
aW9wX3ZlcnNpb24gLS0gQ0FMTEVECjwyMj4gbHZtX2NoZWNrX3NwZWNpYWwgLS0gQ0FMTEVECjwy
Mj4gbHZtX2NoZWNrX3NwZWNpYWwgLS0gTEVBVklORwo8MT4gbHZtX2dldF9pb3BfdmVyc2lvbiAt



Rasmus Wiman wrote:

>Joe Thornber <thornber@btconnect.com> skrev:
>
>>>This evening I added a 36 GB drive to our department server. I did a
>>>vgextend on it and somehow it all went terribly wrong. It seems to me
>>>
>>that
>>
>>>the new drive got added twice, but with different UUIDs. Of course
>>>
>>there
>>
>>>is no way vgchange will bring it online. Is there a solution to the
>>>problem? I downloaded LDE from <http://lde.sourceforge.net/> to have a
>>>look at it, but I don't know what to alter. I run Slackware 8 with
>>>
>>Kernel
>>
>>>2.4.8 and LVM-1.0. The attached files contain output from pvdata -U -V
>>>
>>-PP
>>
>>>on all three partitions.
>>>
>>You're right sdb1 appears to have been added twice with seperate
>>UUID's.  I'm at a loss to explain this at the moment.  Did you run
>>pvcreate more than once on sdb1 ? (I want to know where that extra
>>uuid came from).
>>
>
>Well here's the full story:
>I added the new disk, made a new LVM partition, ran pvcreate on it. Did a
>vgextend vg1 /dev/sdb1. Rebooted. No vg:s found, Panic: root not found.
>Spent a bunch of hours hackaing a Slackware 8 boot floppy with LVM 1.0
>support. It found the vg. Next idea: Maybe it's because of devfs. I hacked
>the disk a bit further yo use devfs, and now it didn't find the VG:s. I
>started looking for any LVM list archive, found something about small
>initrd:s so I put an 8 MB initrd image on the root floppy, and wow, the VG
>was there. Tried to put a larger initrd on the boot partition and re-ran
>lilo. Rebooted, no success. Later I realised that a initrd_size=8912k
>might have done the trick. Booted from the floppy again and did a vgreduce
>vg1 /dev/sdb1. Now it would boot. Here I should really have backed up
>everything to a non LVM partition, but instead I did a vgextend vg1 sdb1.
>Re-ran lvmcreate_initrd, re-ran lilo and rebooted. That's where I am now.
>Two SDB1:s with separate UUID's. Can this be fixed or should I format and
>reinstall? It would really feel bad because I've never had to format and
>reinstall a Linux system except for the occasional hardware failure.
>
>
>---------------------
>Rasmus Wiman
>SAMI Labs
>
>_______________________________________________
>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] My VG is gone...

[AJ Lewis]

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

On Sun, Sep 02, 2001 at 08:07:15PM +0200, Rasmus Wiman wrote:
> Joe Thornber <thornber@btconnect.com> skrev:
> > You're right sdb1 appears to have been added twice with seperate
> > UUID's.  I'm at a loss to explain this at the moment.  Did you run
> > pvcreate more than once on sdb1 ? (I want to know where that extra
> > uuid came from).
> 
> Well here's the full story:
> I added the new disk, made a new LVM partition, ran pvcreate on it. Did a
> vgextend vg1 /dev/sdb1. Rebooted. No vg:s found, Panic: root not found.
> Spent a bunch of hours hackaing a Slackware 8 boot floppy with LVM 1.0
> support. It found the vg. Next idea: Maybe it's because of devfs. I hacked
> the disk a bit further yo use devfs, and now it didn't find the VG:s. I
> started looking for any LVM list archive, found something about small
> initrd:s so I put an 8 MB initrd image on the root floppy, and wow, the VG
> was there. Tried to put a larger initrd on the boot partition and re-ran
> lilo. Rebooted, no success. Later I realised that a initrd_size=8912k
> might have done the trick. Booted from the floppy again and did a vgreduce
> vg1 /dev/sdb1. Now it would boot. Here I should really have backed up
> everything to a non LVM partition, but instead I did a vgextend vg1 sdb1.
> Re-ran lvmcreate_initrd, re-ran lilo and rebooted. That's where I am now.
> Two SDB1:s with separate UUID's. Can this be fixed or should I format and
> reinstall? It would really feel bad because I've never had to format and
> reinstall a Linux system except for the occasional hardware failure.

Did you try the uuid_fixer program at ftp://ftp.sistina.com/pub/LVM/contrib

That may fix your problem, but it would be nice to get as much info out of
your system as possible before you use it to figure out what went wrong...

-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3CD1 25EE DBE3 1B69 F3C7  A1FB 2A81 D686 34A2 2E9E

-----Begin Obligatory Humorous Quote----------------------------------------
Life's short and hard, kind of like a bodybuilding elf
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

RE: [linux-lvm] My VG is gone...

[Diehl, Jeffrey]

I'm having a very similar problem.  When I run vgscan, I get:

[root@filmore jdiehl]# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "Database2"
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get
data of
 volume group "Database2" from physical volume(s)
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" creating
"/etc/lv
mtab" and "/etc/lvmtab.d" 

Any ideas about how to recover without losing my data.  I need to get going
soon, so if I haven't fixed it by late this week, I'm going to reformat....
And lose several Gb of data.

Thanx,
Mike Diehl,
Network Monitoring Tool Devl.
Sandia National Laboratories.
(505) 284-3137
jdiehl@sandia.gov

> -----Original Message-----
> From: AJ Lewis [mailto:lewis@sistina.com]
> Sent: September 04, 2001 6:43 AM
> To: linux-lvm@sistina.com
> Subject: Re: [linux-lvm] My VG is gone...
> 
> 
> On Sun, Sep 02, 2001 at 08:07:15PM +0200, Rasmus Wiman wrote:
> > Joe Thornber <thornber@btconnect.com> skrev:
> > > You're right sdb1 appears to have been added twice with seperate
> > > UUID's.  I'm at a loss to explain this at the moment.  Did you run
> > > pvcreate more than once on sdb1 ? (I want to know where that extra
> > > uuid came from).
> > 
> > Well here's the full story:
> > I added the new disk, made a new LVM partition, ran 
> pvcreate on it. Did a
> > vgextend vg1 /dev/sdb1. Rebooted. No vg:s found, Panic: 
> root not found.
> > Spent a bunch of hours hackaing a Slackware 8 boot floppy 
> with LVM 1.0
> > support. It found the vg. Next idea: Maybe it's because of 
> devfs. I hacked
> > the disk a bit further yo use devfs, and now it didn't find 
> the VG:s. I
> > started looking for any LVM list archive, found something 
> about small
> > initrd:s so I put an 8 MB initrd image on the root floppy, 
> and wow, the VG
> > was there. Tried to put a larger initrd on the boot 
> partition and re-ran
> > lilo. Rebooted, no success. Later I realised that a 
> initrd_size=8912k
> > might have done the trick. Booted from the floppy again and 
> did a vgreduce
> > vg1 /dev/sdb1. Now it would boot. Here I should really have 
> backed up
> > everything to a non LVM partition, but instead I did a 
> vgextend vg1 sdb1.
> > Re-ran lvmcreate_initrd, re-ran lilo and rebooted. That's 
> where I am now.
> > Two SDB1:s with separate UUID's. Can this be fixed or 
> should I format and
> > reinstall? It would really feel bad because I've never had 
> to format and
> > reinstall a Linux system except for the occasional hardware failure.
> 
> Did you try the uuid_fixer program at 
> ftp://ftp.sistina.com/pub/LVM/contrib
> 
> That may fix your problem, but it would be nice to get as 
> much info out of
> your system as possible before you use it to figure out what 
> went wrong...
> 
> -- 
> AJ Lewis
> Sistina Software Inc.                  Voice:  612-638-0500
> 1313 5th St SE, Suite 111              Fax:    612-638-0500
> Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
> http://www.sistina.com
> 
> Current GPG fingerprint = 3CD1 25EE DBE3 1B69 F3C7  A1FB 2A81 
> D686 34A2 2E9E
> 
> -----Begin Obligatory Humorous 
> Quote----------------------------------------
> Life's short and hard, kind of like a bodybuilding elf
> -----End Obligatory Humorous 
> Quote------------------------------------------
> 

Re: [linux-lvm] My VG is gone...

[Rasmus Wiman]

"Diehl, Jeffrey" <jdiehl@sandia.gov> skrev:

> Any ideas about how to recover without losing my data.  I need to get
> going
> soon, so if I haven't fixed it by late this week, I'm going to
> reformat....
> And lose several Gb of data.

I have already reformated my hard disks, alas. I didn't have time to wait
for a solution. But If someone would have helped me or suppllied code that
fixed the problem, it could have beed the start of a Doctor LVM project. I
think there should really be crash recover tools for any file system and
LVM system since they all do crash some times.


---------------------
Rasmus Wiman
SAMI Labs

RE: [linux-lvm] My VG is gone...

[Diehl, Jeffrey]

I will be formating 311Gb of hard drives today.  These drives were 40% full.
This is the second time that LVM has bitten me.  The first time I tried to
expand a VG, the VG was gone when the machine rebooted.  Same thing this
time.  AND THERE IS APEARANTLY NO WAY TO RECOVER!  It seems that all of the
vg data is recorded in each member pv.  So, why isn't there a utility to
recover a vg in this situation?  This is very fragile! 

Mike Diehl.


-----Original Message-----
From: Rasmus Wiman
To: linux-lvm@sistina.com
Sent: 9/5/2001 2:04 AM
Subject: Re: [linux-lvm] My VG is gone...

"Diehl, Jeffrey" <jdiehl@sandia.gov> skrev:

> Any ideas about how to recover without losing my data.  I need to get
> going
> soon, so if I haven't fixed it by late this week, I'm going to
> reformat....
> And lose several Gb of data.

I have already reformated my hard disks, alas. I didn't have time to
wait
for a solution. But If someone would have helped me or suppllied code
that
fixed the problem, it could have beed the start of a Doctor LVM project.
I
think there should really be crash recover tools for any file system and
LVM system since they all do crash some times.


---------------------
Rasmus Wiman
SAMI Labs

_______________________________________________
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] My VG is gone...

[AJ Lewis]

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

On Wed, Sep 05, 2001 at 12:56:10PM -0600, Diehl, Jeffrey wrote:
> I will be formating 311Gb of hard drives today.  These drives were 40% full.
> This is the second time that LVM has bitten me.  The first time I tried to
> expand a VG, the VG was gone when the machine rebooted.  Same thing this
> time.  AND THERE IS APEARANTLY NO WAY TO RECOVER!  It seems that all of the
> vg data is recorded in each member pv.  So, why isn't there a utility to
> recover a vg in this situation?  This is very fragile! 

Did you try the uuid_fixer previously mentioned?

> 
> -----Original Message-----
> From: Rasmus Wiman
> To: linux-lvm@sistina.com
> Sent: 9/5/2001 2:04 AM
> Subject: Re: [linux-lvm] My VG is gone...
> 
> "Diehl, Jeffrey" <jdiehl@sandia.gov> skrev:
> 
> > Any ideas about how to recover without losing my data.  I need to get
> > going
> > soon, so if I haven't fixed it by late this week, I'm going to
> > reformat....
> > And lose several Gb of data.
> 
> I have already reformated my hard disks, alas. I didn't have time to
> wait
> for a solution. But If someone would have helped me or suppllied code
> that
> fixed the problem, it could have beed the start of a Doctor LVM project.
> I
> think there should really be crash recover tools for any file system and
> LVM system since they all do crash some times.
> 
> 
> ---------------------
> Rasmus Wiman
> SAMI Labs
> 
> _______________________________________________
> 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
> 
> 
> _______________________________________________
> 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

-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 60F3 160D C0D5 2C4B 751B  4FF9 6F67 E9BC 44CD DE95

-----Begin Obligatory Humorous Quote----------------------------------------
FATAL ERROR! SYSTEM HALTED! - Press any key to do nothing...
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

RE: [linux-lvm] My VG is gone...

[Diehl, Jeffrey]

Yes, I did try this utility.  Thanx for your suggestion.

Mike Diehl,
Network Monitoring Tool Devl.
Sandia National Laboratories.
(505) 284-3137
jdiehl@sandia.gov

> -----Original Message-----
> From: AJ Lewis [mailto:lewis@sistina.com]
> Sent: September 05, 2001 2:42 PM
> To: linux-lvm@sistina.com
> Subject: Re: [linux-lvm] My VG is gone...
> 
> 
> On Wed, Sep 05, 2001 at 12:56:10PM -0600, Diehl, Jeffrey wrote:
> > I will be formating 311Gb of hard drives today.  These 
> drives were 40% full.
> > This is the second time that LVM has bitten me.  The first 
> time I tried to
> > expand a VG, the VG was gone when the machine rebooted.  
> Same thing this
> > time.  AND THERE IS APEARANTLY NO WAY TO RECOVER!  It seems 
> that all of the
> > vg data is recorded in each member pv.  So, why isn't there 
> a utility to
> > recover a vg in this situation?  This is very fragile! 
> 
> Did you try the uuid_fixer previously mentioned?
> 
> > 
> > -----Original Message-----
> > From: Rasmus Wiman
> > To: linux-lvm@sistina.com
> > Sent: 9/5/2001 2:04 AM
> > Subject: Re: [linux-lvm] My VG is gone...
> > 
> > "Diehl, Jeffrey" <jdiehl@sandia.gov> skrev:
> > 
> > > Any ideas about how to recover without losing my data.  I 
> need to get
> > > going
> > > soon, so if I haven't fixed it by late this week, I'm going to
> > > reformat....
> > > And lose several Gb of data.
> > 
> > I have already reformated my hard disks, alas. I didn't have time to
> > wait
> > for a solution. But If someone would have helped me or 
> suppllied code
> > that
> > fixed the problem, it could have beed the start of a Doctor 
> LVM project.
> > I
> > think there should really be crash recover tools for any 
> file system and
> > LVM system since they all do crash some times.
> > 
> > 
> > ---------------------
> > Rasmus Wiman
> > SAMI Labs
> > 
> > _______________________________________________
> > 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
> > 
> > 
> > _______________________________________________
> > 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
> 
> -- 
> AJ Lewis
> Sistina Software Inc.                  Voice:  612-638-0500
> 1313 5th St SE, Suite 111              Fax:    612-638-0500
> Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
> http://www.sistina.com
> 
> Current GPG fingerprint = 60F3 160D C0D5 2C4B 751B  4FF9 6F67 
> E9BC 44CD DE95
> 
> -----Begin Obligatory Humorous 
> Quote----------------------------------------
> FATAL ERROR! SYSTEM HALTED! - Press any key to do nothing...
> -----End Obligatory Humorous 
> Quote------------------------------------------
>