From: "Diaz Rodriguez, Eduardo" <ediaz@pk25.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] invalid physical volume
Date: Tue, 12 Apr 2005 17:39:19 +0200 [thread overview]
Message-ID: <20050412153719.M45202@pk25.com> (raw)
In-Reply-To: <425BE8C5.4030502@cjs226.com>
try this:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124647
are you the last comment?.
regards!
On Tue, 12 Apr 2005 10:27:01 -0500, Clif Smith wrote
> I receive the same for all commands you requested, for example:
> # pvcreate /dev/emcpowera1
> pvcreate -- invalid physical volume "/dev/emcpowera1"
>
> Diaz Rodriguez, Eduardo wrote:
>
> >try pvcreate /dev/emcpowera1 is for the partition not for the disk...
> >
> >please summarize
> >
> >regards!
> >
> >On Tue, 12 Apr 2005 09:51:20 -0500, Clif Smith wrote
> >
> >
> >>Responses in line.
> >>
> >>Thanks, Clif
> >>
> >>Diaz Rodriguez, Eduardo wrote:
> >>
> >>
> >>
> >>>Clif try to make a partition type linux lvm.. (8e) and after try pvcreate
> >>>
> >>>
> >over it
> >
> >
> >>>
> >>>
> >>>
> >>>
> >># fdisk -l /dev/emcpowera
> >>Disk /dev/emcpowera: 10.7 GB, 10737418240 bytes
> >>255 heads, 63 sectors/track, 1305 cylinders
> >>Units = cylinders of 16065 * 512 = 8225280 bytes
> >> Device Boot Start End Blocks Id System
> >>/dev/emcpowera1 1 1305 10482381 8e Linux LVM
> >>
> >># pvcreate /dev/emcpowera
> >>pvcreate -- invalid physical volume "/dev/emcpowera"
> >>
> >>
> >>
> >>>send a output of pvcreate -v /dev/emcpowera
> >>>
> >>>
> >>>
> >>>
> >># pvcreate -v /dev/emcpowera
> >>pvcreate -- locking logical volume manager
> >>pvcreate -- checking physical volume name "/dev/emcpowera"
> >>pvcreate -- getting physical volume size
> >>pvcreate -- checking maximum physical volume size
> >>pvcreate -- checking partition type
> >>pvcreate -- invalid physical volume "/dev/emcpowera"
> >>
> >>
> >>
> >>>if you complile with debug use pvcreate -dv /dev/emcpowera
> >>>
> >>>
> >>>
> >>>
> >>>
> >># pvcreate -dv /dev/emcpowera
> >><1> lvm_get_iop_version -- CALLED
> >><22> lvm_check_special -- CALLED
> >><22> lvm_check_special -- LEAVING
> >><1> lvm_get_iop_version -- AFTER ioctl ret: 0
> >><1> lvm_get_iop_version -- LEAVING with ret: 10
> >>pvcreate -- locking logical volume manager
> >><1> lvm_lock -- CALLED
> >><22> lvm_check_special -- CALLED
> >><22> lvm_check_special -- LEAVING
> >><1> lvm_lock -- LEAVING with ret: 0
> >>pvcreate -- checking physical volume name "/dev/emcpowera"
> >><1> pv_check_name -- CALLED with "/dev/emcpowera"
> >><22> lvm_check_chars -- CALLED with name: "/dev/emcpowera"
> >><22> lvm_check_chars -- LEAVING with ret: 0
> >><1> pv_check_name -- LEAVING with ret: 0
> >>pvcreate -- getting physical volume size
> >><1> _pv_get_dev_size -- CALLED with /dev/emcpowera and 0xbfffa650
> >><1> _pv_get_dev_size -- LEAVING with ret: 20971520
> >>pvcreate -- checking maximum physical volume size
> >><1> pv_create_kdev_t -- CALLED with "/dev/emcpowera"
> >><22> pv_check_name -- CALLED with "/dev/emcpowera"
> >><333> lvm_check_chars -- CALLED with name: "/dev/emcpowera"
> >><333> lvm_check_chars -- LEAVING with ret: 0
> >><22> pv_check_name -- LEAVING with ret: 0
> >><1> pv_create_kdev_t -- LEAVING with ret: E800
> >><1> lvm_check_partitioned_dev -- CALLED
> >><22> lvm_get_device_type called
> >><22> lvm_get_device_type leaving with -1
> >><1> lvm_check_partitioned_dev -- LEAVING with ret: FALSE
> >>pvcreate -- checking partition type
> >><1> pv_read -- CALLED with /dev/emcpowera
> >><22> pv_check_name -- CALLED with "/dev/emcpowera"
> >><333> lvm_check_chars -- CALLED with name: "/dev/emcpowera"
> >><333> lvm_check_chars -- LEAVING with ret: 0
> >><22> pv_check_name -- LEAVING with ret: 0
> >><1> pv_read -- going to read /dev/emcpowera
> >><22> lvm_check_dev -- CALLED
> >><333> lvm_check_partitioned_dev -- CALLED
> >><4444> lvm_get_device_type called
> >><4444> lvm_get_device_type leaving with -1
> >><333> lvm_check_partitioned_dev -- LEAVING with ret: FALSE
> >><22> lvm_check_dev -- LEAVING with ret: 0
> >><1> pv_read -- LEAVING with ret: -270
> >>pvcreate -- invalid physical volume "/dev/emcpowera"
> >>
> >><1> lvm_unlock -- CALLED
> >><1> lvm_unlock -- LEAVING with ret: 0
> >>
> >>
> >>
> >>>send the error leve returns echo $?
> >>>
> >>>regards!
> >>>
> >>>
> >>>
> >>>On Mon, 11 Apr 2005 21:52:08 -0500, Clif Smith wrote
> >>>
> >>>
> >>>
> >>>
> >>>>I'm running lvm-1.0.8-9 on RHES3 and am receiving the following when
> >>>>I try to utilize a volume from an EMC array:
> >>>># pvcreate /dev/emcpowera
> >>>>pvcreate -- invalid physical volume "/dev/emcpowera"
> >>>>
> >>>>The OS sees the volume fine:
> >>>># fdisk -l /dev/emcpowera
> >>>>Disk /dev/emcpowera: 10.7 GB, 10737418240 bytes
> >>>>255 heads, 63 sectors/track, 1305 cylinders
> >>>>Units = cylinders of 16065 * 512 = 8225280 bytes
> >>>>
> >>>>I can create a partition and then a filesystem without issue, but I
> >>>>really need to use it within LVM.
> >>>>
> >>>>Any ideas?
> >>>>
> >>>>_______________________________________________
> >>>>linux-lvm mailing list
> >>>>linux-lvm@redhat.com
> >>>>https://www.redhat.com/mailman/listinfo/linux-lvm
> >>>>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
>
>>=======================================================================================
> >>
> >>
> >>>La teta que la mano no cubre, no es teta sino ubre.
> >>> -- An�nim.
> >>>
> >>>
>
>>=======================================================================================
> >>
> >>
> >>>_______________________________________________
> >>>linux-lvm mailing list
> >>>linux-lvm@redhat.com
> >>>https://www.redhat.com/mailman/listinfo/linux-lvm
> >>>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >>>
> >>>
> >>>
> >>>
> >>_______________________________________________
> >>linux-lvm mailing list
> >>linux-lvm@redhat.com
> >>https://www.redhat.com/mailman/listinfo/linux-lvm
> >>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >>
> >>
> >
> >
>
>=======================================================================================
> >La teta que la mano no cubre, no es teta sino ubre.
> > -- An�nim.
>
>=======================================================================================
> >
> >_______________________________________________
> >linux-lvm mailing list
> >linux-lvm@redhat.com
> >https://www.redhat.com/mailman/listinfo/linux-lvm
> >read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >
> >
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
=======================================================================================
La teta que la mano no cubre, no es teta sino ubre.
-- An�nim.
=======================================================================================
next prev parent reply other threads:[~2005-04-12 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 2:52 [linux-lvm] invalid physical volume Clif Smith
2005-04-12 8:33 ` Diaz Rodriguez, Eduardo
2005-04-12 14:51 ` Clif Smith
2005-04-12 15:21 ` Diaz Rodriguez, Eduardo
2005-04-12 15:27 ` Clif Smith
2005-04-12 15:39 ` Diaz Rodriguez, Eduardo [this message]
2005-04-12 15:47 ` Clif Smith
2005-04-13 14:55 ` [linux-lvm] invalid physical volume SOLVED (sorta) Clif Smith
2005-04-12 20:11 ` [linux-lvm] invalid physical volume Luca Berra
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=20050412153719.M45202@pk25.com \
--to=ediaz@pk25.com \
--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).