From: Maurizio Marini Gmail <marini.maurizio@gmail.com>
To: linux-lvm@redhat.com
Cc: maumar@datalogica.com
Subject: [linux-lvm] repair a damaged vg
Date: Sun, 20 Dec 2009 01:42:02 +0100 [thread overview]
Message-ID: <784f9de10912191642u482a0141teb09d3958bd7b680@mail.gmail.com> (raw)
sorry for cross-posting with fedora mlists.
after pvcreate /dev/sdc
Physical volume "/dev/sdc" successfully created
sadly i issued:
vgextend /dev/mapper/VolGroup01 /dev/sdc
Volume group "VolGroup01" successfully extended
instead of doing:
vgextend VolGroup01 /dev/sdc
Volume group "VolGroup01" successfully extended
I used the wrong syntax.
then i tryied to extend lv
lvextend -l 100%VG /dev/mapper/VolGroup01-lvol0
Couldn't find device with uuid
'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'.
Extending logical volume lvol0 to 329,99 GB
Cannot update volume group VolGroup01 while physical volumes are missing.
now i tried to assign that uuid to /dev/sdb, sadly w/out success:
================
pvcreate -u qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF --restorefile
/etc/lvm/archive/VolGroup01_00002.vg /dev/sdb
Couldn't find device with uuid
'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'.
Device /dev/sdb not found (or ignored by filtering).
================
pvcreate -ff -u qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF --restorefile
/etc/lvm/archive/VolGroup01_00002.vg /dev/sdb
Couldn't find device with uuid
'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'.
Device /dev/sdb not found (or ignored by filtering).
================
vgreduce -t --removemissing VolGroup01
Test mode: Metadata will NOT be updated.
Couldn't find device with uuid
'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'.
Couldn't find device with uuid
'qf0ApW-42u1-nlyq-2TTn-MIgB-3dT1-BNe3GF'.
WARNING: Partial LV lvol0 needs to be repaired or removed.
WARNING: There are still partial LVs in VG VolGroup01.
To remove them unconditionally use: vgreduce --removemissing
--force.
Proceeding to remove empty missing PVs.
================
is there a clean solution to my fault?
tia
Maurizio
reply other threads:[~2009-12-20 0:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=784f9de10912191642u482a0141teb09d3958bd7b680@mail.gmail.com \
--to=marini.maurizio@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=maumar@datalogica.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).