Thanks Alasdair, your suggestion work.
However, I'm encountering yet another problem....;p
Looks like device-mapper always return an error on "cmd 13" when I
tried to create a lv:
[root@DAP-RHLNX1 2.4.21]# lvcreate -v -L 32 -n syueVol vg00-lvm1
device-mapper ioctl cmd 13 failed: Invalid argument
device-mapper ioctl cmd 13 failed: Invalid argument
Finding volume group "vg00-lvm1"
Creating logical volume syueVol
Archiving volume group "vg00-lvm1" metadata.
Creating volume group backup "/etc/lvm/backup/vg00-lvm1"
Found volume group "vg00-lvm1"
Loading vg00--lvm1-syueVol
Zeroing start of logical volume "syueVol"
Creating volume group backup "/etc/lvm/backup/vg00-lvm1"
Logical volume "syueVol" created
[root@DAP-RHLNX1 2.4.21]#
Here are the version information:
=========================
LVM version 2.2.00.22
Device Mapper version 1.00.18
Does anyone know what the problem is?
Thanks,
Stanley
On Mon, 13 Sep 2004 11:41:34 +0100, Alasdair G Kergon <agk@redhat.com> wrote:
> On Mon, Sep 13, 2004 at 01:58:14AM -0700, Stanley Yue wrote:
> > with the lvm-mod and device-mapper from lvm2. I want to test out
> > whether lvm2 utilities can detect configurations created from lvm1
> > utilities.
>
> > pvcreate -- ERROR: VGDA in kernel and lvmtab are NOT consistent;
> > please run vgscan
>
> Never run LVM2 utilities while you have LVs active under LVM1.
> Never run LVM1 tools while you have LVs active under LVM2.
>
> i.e. Never mix use of the two, and always vgchange -an before switching
> between LVM1 and LVM2.
> Also, if switching back from LVM2 to LVM1 you must first reset the
> LVM1 driver with lvmchange -R followed by vgscan -f.
>
> Alasdair
> --
> agk@redhat.com
>
_______________________________________________
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/
