From: YouMizuki <appendix@hatsune.cc>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgscanfailed"novolumegroupsfound"
Date: Thu Oct 25 10:23:02 2001 [thread overview]
Message-ID: <20011026003002.5332.APPENDIX@hatsune.cc> (raw)
In-Reply-To: <20011025014038.X23590@turbolinux.com>
>> My VG structure is following
>> /dev/md2,md3,md4,md5,md6,md7,md8,md9,md10 => vg0
>You say 9 md devices, and list 9 above for vg0.
>pvscan -- inactive PV "/dev/md10" of VG "vg1" [4.48 GB / 4.48 GB free]
>One of your PVs says it is in another VG ^^^ very strange.
This PV device is not used now.This PV is not included "vg0"
# Really,this device was included "vg0",but when I tried to recovery this,
# It was broken ,cause of my mistake.
# It may be broken part of this VG, but I think the area will be not used by filesystem.
# I want to recovery remaining....
>> >pvdata -PP pvdata -PP /dev/md2
>> --- Physical volume ---
>> PV# 2
>> PV UUID gyivka-8v8R-s8N6-UHW1-mXO2-A7pe-3V2UtL
>This matches "001" above. You need to check each of the other MD devices
>to see which ones have valid UUIDs. You may need to use the uuid-fixer
>tool.
Thanks! I will try to use uuid-fixer.
--
YouMizuki <appendix@hatsune.cc>
next prev parent reply other threads:[~2001-10-25 10:23 UTC|newest]
Thread overview: 8+ 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 [this message]
2001-10-27 5:33 ` [linux-lvm] vgscan failed "no volume groups found" YouMizuki
2001-10-29 12:38 ` [linux-lvm] trouble of reduce pv YouMizuki
2001-10-29 16:17 ` Heinz J . Mauelshagen
2001-10-29 19:35 ` YouMizuki
-- strict thread matches above, loose matches on Subject: below --
2001-10-25 2:37 [linux-lvm] vgscanfailed"novolumegroupsfound" appendix
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=20011026003002.5332.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).