From: "Cisco" <cisco66@gmx.de>
To: 'LVM general discussion and development' <linux-lvm@redhat.com>
Subject: [linux-lvm] please help: unable to get rid of LV
Date: Fri, 16 Jun 2006 13:35:25 +0200 [thread overview]
Message-ID: <20060616113527.DCB4275706@mailer.at.ds9> (raw)
In-Reply-To: <449194DD.6070801@poczta.onet.pl>
Hi,
i have the following setup:
/dev/md2 --RAID1 (2x250GB)
/dev/md0 --RAID-5 (4x160GB)
both md-devices are added to LVM (2)
Library version: 1.02.03 (2006-02-08)
Driver version: 4.3.0
There are 1 VG and 10 LV's created. VG00 and LV00-LV09
Everything worked fine until i obviously did a mistake rezising the LV06.
(I resized othe LV's without problem before but with LV06 i forgot something
...)
Now i moved all other LV's to /dev/md0 with pvmove -n ..., exept for LV06
However i couldn't "lvremove" the LV06 (error: can't remove open lv or so)
I wasn't also able to deactivate the lv nor the vg.
So i tried to pvremove -ff the /dev/md2 PV (maybe the first big mistake)
Then i did a pvcreate on /dev/md2 again.
Now everything seems to be messed up:
#pvdisplay
Couldn't find device with uuid 'faoJTZ-VDvh-Gqtd-V0jJ-qbMD-w8be-RvV4Dq'.
--- Physical volume ---
PV Name unknown device
VG Name vg00
PV Size 232,88 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 59618
Free PE 51938
Allocated PE 7680
PV UUID faoJTZ-VDvh-Gqtd-V0jJ-qbMD-w8be-RvV4Dq
--- Physical volume ---
PV Name /dev/md0
VG Name vg00
PV Size 460,16 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 117800
Free PE 63272
Allocated PE 54528
PV UUID eydC5O-MF3B-oysT-KvoA-pu1D-o54H-GpPmkL
--- NEW Physical volume ---
PV Name /dev/md2
VG Name
PV Size 232,89 GB
Allocatable NO
PE Size (KByte) 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID L4624h-V1WS-AaXi-4leU-6QBD-9Cs6-4d3NBt
The "unknown" device still contains the data of LV06. This data is not
important so i just want consistency back.
#lvremove vg00/lv06
Couldn't find device with uuid 'faoJTZ-VDvh-Gqtd-V0jJ-qbMD-w8be-RvV4Dq'.
Couldn't find all physical volumes for volume group vg00.
Couldn't find device with uuid 'faoJTZ-VDvh-Gqtd-V0jJ-qbMD-w8be-RvV4Dq'.
Couldn't find all physical volumes for volume group vg00.
Volume group "vg00" not found
Also, my cryptsetup gives errors:
#/etc/init.d/cryptdisks start
Starting crypto disks: clv00(starting)...
Command failed: Es ist ein Block-Device notwendig (a block device is
necessary)
clv01(starting)...
Command failed: Es ist ein Block-Device notwendig
clv02(starting)...
Command failed: Es ist ein Block-Device notwendig
clv04(starting)...
Command failed: Es ist ein Block-Device notwendig
clv05(starting)...
Command failed: Es ist ein Block-Device notwendig
clv07(starting)...
Command failed: Es ist ein Block-Device notwendig
clv08(starting)...
Command failed: Es ist ein Block-Device notwendig
clv09(starting)...
Command failed: Es ist ein Block-Device notwendig
swap0(running) swap1(running).
Any ideas what i can do now ?
Thanks in advance,
next prev parent reply other threads:[~2006-06-16 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 17:11 [linux-lvm] lvm -> "normal" system conversion Maciej Słojewski
2006-06-15 17:56 ` Dieter Stüken
2006-06-16 16:20 ` Maciej Słojewski
2006-06-16 11:35 ` Cisco [this message]
2006-06-16 12:11 ` AW: [linux-lvm] please help: unable to get rid of LV Cisco
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=20060616113527.DCB4275706@mailer.at.ds9 \
--to=cisco66@gmx.de \
--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).