From: Sam Vilain <sam@vilain.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] PVs that are reused / reformatted as filesystems
Date: Wed, 22 Dec 2004 14:57:32 +1300 [thread overview]
Message-ID: <41C8D48C.6090908@vilain.net> (raw)
In-Reply-To: <20041221181601.GJ26670@agk.surrey.redhat.com>
Alasdair G Kergon wrote:
>>Could someone please give me a fish (tell me how to un-jam my LVM) and
>>maybe even teach the LVM drivers/utilities to fish as well?
> Use pvscan / pvs -v to work out which devices you want to see and which you don't
> then change the filter in /etc/lvm/lvm.conf so you only see the right ones.
Thanks Alasdair.
It looks like my problem is actually deeper than I originally thought;
# vgdisplay -v foobar
[snip]
--- Physical volumes ---
PV Name /dev/hda2
PV UUID weM5FG-L0Li-Ir7y-0B2z-MJoq-tvAg-C2Q19E
PV Status allocatable
Total PE / Free PE 16672 / 0
PV Name /dev/hda1
PV UUID 85M9M7-QsLh-dVKf-xfU3-ua4h-Ks4h-QGrMhu
PV Status allocatable
Total PE / Free PE 3578 / 26
PV Name unknown device
PV UUID PtbIxo-EmRo-ML7J-yhqx-gglD-ZayH-X6tuWE
PV Status allocatable
Total PE / Free PE 4535 / 4535
Hmm, now how can I use vgreduce on an read-only VG to remove an unknown
PV?
# vgreduce --removemissing foobar
Gone.
--
Sam Vilain, sam /\T vilain |><>T net, PGP key ID: 0x05B52F13
(include my PGP key ID in personal replies to avoid spam filtering)
next prev parent reply other threads:[~2004-12-22 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 4:10 [linux-lvm] PVs that are reused / reformatted as filesystems Sam Vilain
2004-12-21 18:16 ` Alasdair G Kergon
2004-12-22 1:57 ` Sam Vilain [this message]
2004-12-21 18:18 ` Alasdair G Kergon
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=41C8D48C.6090908@vilain.net \
--to=sam@vilain.net \
--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 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.