From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm problem
Date: Tue Jan 15 05:56:01 2002 [thread overview]
Message-ID: <20020115125319.A11005@sistina.com> (raw)
In-Reply-To: <OF5335B286.82ADE051-ONC1256B41.004E7A11@hpigmbh.com>; from Matthias.Stoll@eu.icgcommerce.com on Mon, Jan 14, 2002 at 03:21:39PM +0100
On Mon, Jan 14, 2002 at 03:21:39PM +0100, Matthias Stoll wrote:
> Hi !
>
> I'm not so firm in linux but:
>
> We had a LG "smbdata" which went away somehow? ;-)
Hi Matthias.
What does 'somehow' mean? ;-)
LVM/Operator error? I know: in case of an operator error I wouldn't tell
anybody either ;-)
>
> Searched all threads and followed your instructions on recovering
> configuration of LV. Didn't work ;-(
>
> Here is the output of vgcfgrestore -ll -f /etc/lvmconf/smbdata.conf.7.old
> -n smbdata /dev/sda
>
> --- Volume group ---
> VG Name smbdata
> VG Access read/write
> VG Status NOT available/resizable
> VG # 0
> MAX LV 256
> Cur LV 1
> Open LV 0
> MAX LV Size 255.99 GB
> Max PV 256
> Cur PV 4
> Act PV 4
> VG Size 15.86 GB
> PE Size 4 MB
> Total PE 4060
> Alloc PE / Size 4060 / 15.86 GB
> Free PE / Size 0 / 0
> VG UUID zwceZi-TCXm-Ew3a-A5yc-H49M-R1NP-y4qg4T
>
> --- Logical volume ---
> LV Name /dev/smbdata/all
> VG Name smbdata
> LV Write Access read/write
> LV Status available
> LV # 1
> # open 0
> LV Size 15.86 GB
> Current LE 4060
> Allocated LE 4060
> Allocation next free
> Read ahead sectors 120
> Block device 58:0
>
>
> --- Physical volume ---
> PV Name /dev/sda1
> VG Name smbdata
> PV Size 3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
> PV# 1
> PV Status NOT available
> Allocatable yes (but full)
> Cur LV 1
> PE Size (KByte) 4096
> Total PE 1015
> Free PE 0
> Allocated PE 1015
> PV UUID tFA0qy-8u7r-8oBv-MwYS-SUVM-1W7h-P3hHED
>
> --- Physical volume ---
> PV Name /dev/sdb1
> VG Name smbdata
> PV Size 3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
> PV# 2
> PV Status NOT available
> Allocatable yes (but full)
> Cur LV 1
> PE Size (KByte) 4096
> Total PE 1015
> Free PE 0
> Allocated PE 1015
> PV UUID cVeBuv-1i2C-hkOO-mUA1-lNrj-Vh8l-vrr6Am
>
> --- Physical volume ---
> PV Name /dev/sdc1
> VG Name smbdata
> PV Size 3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
> PV# 3
> PV Status NOT available
> Allocatable yes (but full)
> Cur LV 1
> PE Size (KByte) 4096
> Total PE 1015
> Free PE 0
> Allocated PE 1015
> PV UUID Rtuhx3-0HR9-V0hN-iLuZ-dkFL-hyih-cEwEII
>
> --- Physical volume ---
> PV Name /dev/sdd1
> VG Name smbdata
> PV Size 3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
> PV# 4
> PV Status NOT available
> Allocatable yes (but full)
> Cur LV 1
> PE Size (KByte) 4096
> Total PE 1015
> Free PE 0
> Allocated PE 1015
> PV UUID HNkTzu-Ok46-4vqM-CJCu-Iqd1-JmQ4-c5yzea
>
>
> Could anyone provide me some help?
Please run:
# save your LVM metadata for later use
for d in /dev/sd[a-d]1; do
dd if=$d of=$d.VGDA count=512 bs=1k
done
# to recreate your PVs because vgcfgrestore needs that
pvcreate -ff /dev/sd[a-d]1
# restore the metadata from backup
for d in /dev/sd[a-d]1; do
vgcfgrestore -n smbdata -f /etc/lvmconf/smbdata.conf.7.old /dev/$d
done
# scan in the metadata
vgscan
# activate the VG
vgchange -ay smbdata
>
> Thanx
>
> Matthias
--
Regards,
Heinz -- The LVM Guy --
*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-01-15 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 8:22 [linux-lvm] lvm problem Matthias Stoll
2002-01-15 5:56 ` Heinz J . Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-06 10:06 Sachin Sant
2004-07-08 10:30 ` Sachin Sant
2008-04-30 23:05 [linux-lvm] LVM problem Subzwari, Junaid
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=20020115125319.A11005@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox