From: YouMizuki <appendix@hatsune.cc>
To: linux-lvm@sistina.com
Subject: [linux-lvm] trouble of reduce pv
Date: Mon Oct 29 12:38:02 2001 [thread overview]
Message-ID: <20011030032905.93E1.APPENDIX@hatsune.cc> (raw)
In-Reply-To: <20011025014038.X23590@turbolinux.com>
I've a LVM one physical volume "vg0" that created on 10 RAID devices.
It worked still the day.
But one day, I have problem about vgscan reports that it can't find my VG.
My VG structure was this.
| /dev/md1,md2,md3,md4,md5,md6,md7,md8,md9,md10 => vg0
But md10 was broken.
I need to restruct VG like this.
| /dev/md1,md2,md3,md4,md5,md6,md7,md8,md9 => vg0
But vgscan is can't find VG
|vgscan
|vgscan -- reading all physical volumes (this may take a while...)
|vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
|vgscan -- WARNING: This program does not do a VGDA backup of your volume group
I tried uuid_fixer. but I get only error.
|uuid_fixer /dev/md1 /dev/md2 /dev/md3 /dev/md4 /dev/md5 /dev/md6 /dev/md7 /dev/md8 /dev/md9
|Error: number of PVs passed in does not match number of PVs in /dev/md2's VG
| 9 PVs were passed in and 10 were expected.
I tried pvmove...
|pvmove --force -v /dev/md9 /dev/md10
|pvmove -- checking name of source physical volume "/dev/md9"
|pvmove -- locking logical volume manager
|pvmove -- reading data of source physical volume from "/dev/md9"
|pvmove -- checking volume group existence
|pvmove -- ERROR: can't move physical extents: volume group vg0 doesn't exist
How do I carry out the restructuring of it and can I reconstruct it?
next prev parent reply other threads:[~2001-10-29 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 0:14 [linux-lvm] vgscanfailed"novolumegroupsfound" appendix
2001-10-25 2:39 ` Andreas Dilger
2001-10-25 10:23 ` YouMizuki
2001-10-27 5:33 ` [linux-lvm] vgscan failed "no volume groups found" YouMizuki
2001-10-29 12:38 ` YouMizuki [this message]
2001-10-29 16:17 ` [linux-lvm] trouble of reduce pv Heinz J . Mauelshagen
2001-10-29 19:35 ` YouMizuki
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=20011030032905.93E1.APPENDIX@hatsune.cc \
--to=appendix@hatsune.cc \
--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;
as well as URLs for NNTP newsgroup(s).