All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Cc: mge@sistina.com
Subject: Re: [linux-lvm] vgcfgrestore error !
Date: Fri Nov 23 07:41:02 2001	[thread overview]
Message-ID: <20011123143532.C4829@sistina.com> (raw)
In-Reply-To: <3BFA4184.43FC7D35@LTUtech.com>; from Igor.Dumaire@LTUtech.com on Tue, Nov 20, 2001 at 12:41:56PM +0100

Igor,

pvdata output looks fine.

Could you send me the metadata for further investigation in private
email, please?

You can retrieve 3 files with the metadata of your PVs by "
for d in /dev/hd[cef]1
do
   dd if=$d of=`basename $d`.lvm bs=1k count=512
done

Regards,
Heinz    -- The LVM Guy --


On Tue, Nov 20, 2001 at 12:41:56PM +0100, Igor Dumaire wrote:
> 
> > Strange.
> > Please provide "vgdisplay -v;pvscan;lvmdiskscan" and "pvdata -PP" for all
> > PVs belonging to the missing VG.
> > 
> # vgdisplay -v
> --- Volume group ---
> VG Name               lvm2
> VG Access             read/write
> VG Status             available/resizable
> VG #                  0
> MAX LV                255
> Cur LV                1
> Open LV               1
> MAX LV Size           255.99 GB
> Max PV                255
> Cur PV                3
> Act PV                3
> VG Size               171.79 GB
> PE Size               4.00 MB
> Total PE              43977
> Alloc PE / Size       43776 / 171.00 GB
> Free  PE / Size       201 / 804.00 MB
> VG UUID               Jp3gDv-ib7D-p5te-FFLZ-lNjI-5brK-fzjEM6
> 
> --- Logical volume ---
> LV Name                /dev/lvm2/Backup
> VG Name                lvm2
> LV Write Access        read/write
> LV Status              available
> LV #                   1
> # open                 1
> LV Size                171.00 GB
> Current LE             43776
> Allocated LE           43776
> Allocation             next free
> Read ahead sectors     120
> Block device           58:0
> 
> 
> --- Physical volumes ---
> PV Name (#)           /dev/hdd1 (3)
> PV Status             available / allocatable
> Total PE / Free PE    14659 / 201
> 
> PV Name (#)           /dev/hdg1 (1)
> PV Status             available / allocatable
> Total PE / Free PE    14659 / 0
> 
> PV Name (#)           /dev/hdh1 (2)
> PV Status             available / allocatable
> Total PE / Free PE    14659 / 0
> 
> 
> 
> # pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- inactive PV "/dev/hdc1"  is associated to an unknown VG (run vgscan)
> pvscan -- ACTIVE   PV "/dev/hdd1" of VG "lvm2" [57.26 GB / 804.00 MB free]
> pvscan -- inactive PV "/dev/hde1"  is associated to an unknown VG (run vgscan)
> pvscan -- inactive PV "/dev/hdf1"  is associated to an unknown VG (run vgscan)
> pvscan -- ACTIVE   PV "/dev/hdg1" of VG "lvm2" [57.26 GB / 0 free]
> pvscan -- ACTIVE   PV "/dev/hdh1" of VG "lvm2" [57.26 GB / 0 free]
> pvscan -- total: 6 [343.62 GB] / in use: 6 [343.62 GB] / in no VG: 0 [0]
> 
> # man pvdata
> # pvdata -PP /dev/hde1
> --- Physical volume ---
> PV Name               /dev/hde1
> VG Name               lvm1
> PV Size               57.27 GB / NOT usable 8.11 MB [LVM: 181.00 KB]
> PV#                   1
> PV Status             NOT available
> Allocatable           yes (but full)
> Cur LV                1
> PE Size (KByte)       4096
> Total PE              14659
> Free PE               0
> Allocated PE          14659
> PV UUID               kbvz5r-hJlN-WU9Q-7xwj-alJ6-8UfO-jopMFc
> pv_dev                   0:33
> system_id                courcelles.ltutech.com1004974292
> 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          4259840
> 
> 
> 
> # pvdata -PP /dev/hdf1
> --- Physical volume ---
> PV Name               /dev/hdf1
> VG Name               lvm1
> PV Size               57.27 GB / NOT usable 8.11 MB [LVM: 181.00 KB]
> PV#                   2
> PV Status             NOT available
> Allocatable           yes (but full)
> Cur LV                1
> PE Size (KByte)       4096
> Total PE              14659
> Free PE               0
> Allocated PE          14659
> PV UUID               weQY7t-7II0-7t74-hVI5-Dj8Y-CV0O-8CyGqh
> pv_dev                   0:33
> system_id                courcelles.ltutech.com1004974293
> 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          4259840
>  
>  
>  
> # pvdata -PP /dev/hdc1
> --- Physical volume ---
> PV Name               /dev/hdc1
> VG Name               lvm1
> PV Size               57.27 GB / NOT usable 8.11 MB [LVM: 181.00 KB]
> PV#                   3
> PV Status             available
> Allocatable           yes
> Cur LV                1
> PE Size (KByte)       4096
> Total PE              14659
> Free PE               201
> Allocated PE          14458
> PV UUID               BFvA7F-ccvF-e5r1-3QH7-02JG-dH4r-AOYF64
> pv_dev                   0:22
> system_id                courcelles.ltutech.com1004974291
> 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          4259840
> 
> 
> Thanks a lot for your help. I have lost (can't acces) a lot of data !
> Best regards.
> 
> -- 
> Igor Dumaire
> 
> www.LTUtech.com - Making Sense of Visual Content
> ------------------------------------------------
> 
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-11-23  7:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19  4:57 [linux-lvm] vgcfgrestore error ! Igor Dumaire
2001-11-19  6:02 ` Heinz J . Mauelshagen
2001-11-19  6:12   ` Igor Dumaire
2001-11-19  6:17   ` Igor Dumaire
2001-11-19  8:23     ` Heinz J . Mauelshagen
2001-11-19  9:21       ` Igor Dumaire
2001-11-20  5:25         ` Heinz J . Mauelshagen
2001-11-20  5:40           ` Igor Dumaire
2001-11-23  7:41             ` Heinz J . Mauelshagen [this message]
2001-11-20 12:54           ` Igor Dumaire
2001-11-20 13:24           ` Igor Dumaire
2001-11-20 12:40   ` Sébastien Riccio

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=20011123143532.C4829@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.com \
    --cc=mge@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.