From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Fwd: why can create the volumn group by vgcreate ?
Date: Sun, 9 Jul 2006 17:21:07 +0200 [thread overview]
Message-ID: <20060709152107.GA22460@percy.comedia.it> (raw)
In-Reply-To: <212696550607090633w568b6056u779486d65b422339@mail.gmail.com>
On Sun, Jul 09, 2006 at 09:33:14PM +0800, zhihang wang wrote:
>sudo pvdisplay /dev/hda2
> --- NEW Physical volume ---
> PV Name /dev/evms/hda2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>Why can't find physical volume label from /dev/hda2?
Because you are using evms.
try using /dev/evms/hda2 as a device name instead.
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2006-07-09 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 7:24 [linux-lvm] why can create the volumn group by vgcreate ? zhihang wang
2006-07-09 13:33 ` [linux-lvm] Fwd: " zhihang wang
2006-07-09 15:21 ` Luca Berra [this message]
2006-07-09 21:58 ` [linux-lvm] vgscan -- ERROR "pv_read_pe(): PV size invalid" Simon Klaiber
2006-07-13 8:42 ` Simon Klaiber
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=20060709152107.GA22460@percy.comedia.it \
--to=bluca@comedia.it \
--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).