All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Severe problem: data lost while adding a partition
Date: Mon Feb  3 04:35:01 2003	[thread overview]
Message-ID: <20030203113148.B8501@sistina.com> (raw)
In-Reply-To: <3E3C62E4.7030409@home.nl>; from s.alberink@home.nl on Sun, Feb 02, 2003 at 01:14:28AM +0100

Sander,

can you tell what you mean with
'...something went horribly wron during install...' ?

Any particular messages which can help analyzing this ?

If you don't have any, take your most recent LVM metedata from the archive 
(/etc/lvconf/ ; you've got a backup, right ?), figure out disks used as PVs
with "vgcfgrestore -ll ..." and run "pvcreate -ff ..." and vgcfgrestore
on all of them. The archive you use shall _not_ include the recently added
disk.

Regards,
Heinz    -- The LVM Guy --


On Sun, Feb 02, 2003 at 01:14:28AM +0100, Sander Alberink wrote:
> Hello all,
> 
> I write to you with a rather grave problem. I have a small LVM setup at 
> home, consisting of 4 partitions. These were created by the Mandrake 8.2 
>   installation system. After deciding to upgrade the system to Mandrake 
> 9.0, I found out that I had another partition lying around which was 
> also prepared for LVM use. I had meant for that disc to use later on in 
>   a different scheme for my /usr partition but never got around to do it.
> However, during installation I decided to add it to the LVM. The idea 
> was that I would extend the FS later (of course, I was not going to 
> involve this LVM setup in the rest of the installation, I would do all 
> that manually.)
> 
> But as you probably guessed, something went horribly wrong during 
> install time and my LVM setup is properly hosed. I wanted to re-create 
> the setup, but alas: I forgot which was the disk that I added.
> 
> The name of the LV (there was only 1) was home, the disks involved were 
> /dev/hda1, /dev/hda[4-6].
> 
> Output of pvscan:
> ----------------------------------------------------------------------
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- walking through all physical volumes found
> pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part1"  is 
> associated to an unknown VG (run vgscan)
> pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part4"  is 
> associated to an unknown VG (run vgscan)
> pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part5"  is 
> associated to an unknown VG (run vgscan)
> pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part6"  is 
> associated to an unknown VG (run vgscan)
> pvscan -- inactive PV "/dev/ide/host0/bus0/target0/lun0/part7"  is 
> associated to an unknown VG (run vgscan)
> pvscan -- total: 5 [1.97 GB] / in use: 5 [1.97 GB] / in no VG: 0 [0]
> 
> -----------------------------------------------------------------------
> 
> output of vgscan:
> -----------------------------------------------------------------------
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume 
> group
> 
> -----------------------------------------------------------------------
> 
> output of pvdisplay /dev/hda1 (this partition belonged to the LV for sure)
> -----------------------------------------------------------------------
> pvdisplay -- getting physical volume size
> --- Physical volume ---
> PV Name               /dev/ide/host0/bus0/target0/lun0/part1
> VG Name               home
> PV Size               399.62 MB / NOT usable 3.62 MB [LVM: 121.00 KB]
> PV#                   1
> PV Status             NOT available
> Allocatable           yes (but full)
> Cur LV                1
> PE Size (KByte)       4096
> Total PE              99
> Free PE               0
> Allocated PE          99
> PV UUID               NCf9U6-nqVy-zn3K-upFo-S0PB-SFqb-o2ERjs
> -----------------------------------------------------------------------
> 
> If you need any further information, please let me know!
> I do hope you can help me with this, since I stand to loose a lot of 
> personal data, of which exists no backup (of course, you guys probably 
> hear this all the time).
> 
> Best regards,
> 
> Sander Alberink
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-02-03  4:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-01 18:15 [linux-lvm] Severe problem: data lost while adding a partition Sander Alberink
2003-02-03  4:35 ` Heinz J . Mauelshagen [this message]
2003-02-06 15:49   ` Sander Alberink
2003-02-07  8:31     ` Heinz J . Mauelshagen
2003-02-17 16:12       ` Sander Alberink
2003-02-17 16:17         ` Steven Lembark
2003-02-25 16:43           ` Sander Alberink
2003-03-04 15:07             ` Sander Alberink
  -- strict thread matches above, loose matches on Subject: below --
2003-02-01 18:15 Sander Alberink

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030203113148.B8501@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.