From: "Thomas Novin" <thnov@xyz.pp.se>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Ran vgreduce --missing to remove broken disk, am I screwed?
Date: Fri, 18 Aug 2006 16:29:26 +0200 [thread overview]
Message-ID: <000001c6c2d2$b5ceafa0$0a00000a@thomas> (raw)
Hi all,
I had a disk that stopped working. After booting I could see with pvdisplay
that the disk was missing. After reading everything I could find via google
I thought that you were supposed to run 'vgreduce --remove-missing volgrp0'
to remove the missing disk from the group.
After this the volume group looks OK but the entire logical volume got
removed! Am I screwed now or is there any way to salvage the data which is
on the remaining three disks?
[root@mistik ~]# pvdisplay
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
--- Physical volume ---
PV Name /dev/sda
VG Name volgrp0
PV Size 189.92 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 48620
Free PE 0
Allocated PE 48620
PV UUID zyELIl-MgM6-9zoD-G0PI-c1Wy-CZ1i-Sps8EV
--- Physical volume ---
PV Name /dev/hdd
VG Name volgrp0
PV Size 115.04 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 29449
Free PE 0
Allocated PE 29449
PV UUID yIgADr-5HXP-lFZC-KtZq-onX2-vaNG-aFiLLI
--- Physical volume ---
PV Name unknown device
VG Name volgrp0
PV Size 115.04 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 29449
Free PE 0
Allocated PE 29449
PV UUID dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53
--- Physical volume ---
PV Name /dev/hda4
VG Name volgrp0
PV Size 111.17 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 28460
Free PE 0
Allocated PE 28460
PV UUID Lh7KKJ-OGDQ-Gv4A-4l7U-TRGS-mfma-R2LrPt
[root@mistik ~]# vgreduce --removemissing volgrp0
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find all physical volumes for volume group volgrp0.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find all physical volumes for volume group volgrp0.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find all physical volumes for volume group volgrp0.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find all physical volumes for volume group volgrp0.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find all physical volumes for volume group volgrp0.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find all physical volumes for volume group volgrp0.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Couldn't find device with uuid 'dvPVGp-9Vcg-b6Gp-s4cC-2pwK-cvyc-ATbE53'.
Wrote out consistent volume group volgrp0
[root@mistik ~]# vgdisplay
--- Volume group ---
VG Name volgrp0
System ID
Format lvm2
Metadata Areas 3
Metadata Sequence No 9
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 3
Act PV 3
VG Size 416.13 GB
PE Size 4.00 MB
Total PE 106529
Alloc PE / Size 0 / 0
Free PE / Size 106529 / 416.13 GB
VG UUID 5C4Hnl-YVct-jtv9-HM5Z-J63D-XePc-ANcpx8
[root@mistik ~]# lvdisplay
[root@mistik ~]#
[root@mistik ~]# pvdisplay
--- Physical volume ---
PV Name /dev/sda
VG Name volgrp0
PV Size 189.92 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 48620
Free PE 48620
Allocated PE 0
PV UUID zyELIl-MgM6-9zoD-G0PI-c1Wy-CZ1i-Sps8EV
--- Physical volume ---
PV Name /dev/hdd
VG Name volgrp0
PV Size 115.04 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 29449
Free PE 29449
Allocated PE 0
PV UUID yIgADr-5HXP-lFZC-KtZq-onX2-vaNG-aFiLLI
--- Physical volume ---
PV Name /dev/hda4
VG Name volgrp0
PV Size 111.17 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 28460
Free PE 28460
Allocated PE 0
PV UUID Lh7KKJ-OGDQ-Gv4A-4l7U-TRGS-mfma-R2LrPt
Thanks for any help on this,
Thomas
next reply other threads:[~2006-08-18 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 14:29 Thomas Novin [this message]
2006-08-29 21:02 ` [linux-lvm] Ran vgreduce --missing to remove broken disk, am I screwed? Thomas Novin
2006-08-29 21:16 ` Peter Smith
2006-08-30 2:16 ` Tom+Dale
2006-08-30 3:09 ` Tom+Dale
2006-09-04 4:09 ` [linux-lvm] Wrecked Logical Volume with vgreduce --removemissing Tom+Dale
2006-09-06 16:29 ` Peter Smith
2006-09-07 17:18 ` Peter Smith
2006-09-11 19:05 ` Tom+Dale
2006-09-12 18:06 ` Peter Smith
2006-09-10 17:27 ` Nix
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='000001c6c2d2$b5ceafa0$0a00000a@thomas' \
--to=thnov@xyz.pp.se \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).