* [linux-lvm] Error on lvcreate or lvremove!
@ 2002-05-21 16:48 bo
2002-05-22 7:50 ` Heinz J . Mauelshagen
0 siblings, 1 reply; 8+ messages in thread
From: bo @ 2002-05-21 16:48 UTC (permalink / raw)
To: linux-lvm
[-- Attachment #1: Type: text/plain, Size: 4960 bytes --]
Hello,
I did not have this kind of problem before but I installed LVM1.1-rc2,
I am experiencing the following errors;
Problem1) could not create an LV from RAID1 vol group
[root@localhost /]# lvcreate -l 496 -n lvraid1 volRaid1
lvcreate -- ERROR "Operation not permitted" opening logical volume "/dev/volRaid1/lvraid1"
Problem2) I could not remove it
[root@localhost /]# lvremove /dev/volRaid1/lvraid1
lvremove -- do you really want to remove "/dev/volRaid1/lvraid1"? [y/n]: y
lvremove -- ERROR "lv_release(): LV number" releasing logical volume "/dev/volRaid1/lvraid1"
Problem3) I could not create a striped LV
[root@localhost /]# lvcreate -l200 -i2 -I4 -n lvjb2s volDisk2
lvcreate -- not enough allocatable/free physical volume space in "volDisk2"
lvcreate -- please check, if physical volumes are allocatable
Attched are more system information.
Please provide me your help,
Thanks,
Bo
[root@localhost /]# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE PV "/dev/md0" of VG "volRaid0" [1.95 GB / 1.95 GB free]
pvscan -- ACTIVE PV "/dev/md1" of VG "volRaid0" [1.95 GB / 1.95 GB free]
pvscan -- ACTIVE PV "/dev/md2" of VG "volRaid0" [1.95 GB / 1.95 GB free]
pvscan -- ACTIVE PV "/dev/md3" of VG "volRaid1" [992 MB / 992 MB free]
pvscan -- ACTIVE PV "/dev/md4" of VG "volRaid1" [992 MB / 992 MB free]
pvscan -- ACTIVE PV "/dev/md5" of VG "volRaid5" [1.95 GB / 1.95 GB free]
pvscan -- ACTIVE PV "/dev/md6" of VG "volRaid5" [1.95 GB / 1.95 GB free]
pvscan -- ACTIVE PV "/dev/hdc9" of VG "volDisk" [992 MB / 992 MB free]
pvscan -- ACTIVE PV "/dev/hdc10" of VG "volDisk2" [992 MB / 992 MB free]
pvscan -- ACTIVE PV "/dev/hdd9" of VG "volDisk" [992 MB / 992 MB free]
pvscan -- ACTIVE PV "/dev/hdd10" of VG "volDisk2" [992 MB / 992 MB free]
pvscan -- ACTIVE PV "/dev/hda15" of VG "volDisk" [996 MB / 996 MB free]
pvscan -- ACTIVE PV "/dev/hda16" of VG "volDisk2" [996 MB / 996 MB free]
pvscan -- total: 13 [17.59 GB] / in use: 13 [17.59 GB] / in no VG: 0 [0]
[root@localhost /]# vgdisplay
--- Volume group ---
VG Name volRaid0
VG Access read/write
VG Status available/resizable
VG # 2
MAX LV 256
Cur LV 0
Open LV 0
MAX LV Size 255.99 GB
Max PV 256
Cur PV 3
Act PV 3
VG Size 5.84 GB
PE Size 4 MB
Total PE 1496
Alloc PE / Size 0 / 0
Free PE / Size 1496 / 5.84 GB
VG UUID 89ZFBj-yaQ0-c26m-uKgF-YhvG-2lGR-C8cvWm
--- Volume group ---
VG Name volRaid1
VG Access read/write
VG Status available/resizable
VG # 3
MAX LV 256
Cur LV 0
Open LV 0
MAX LV Size 255.99 GB
Max PV 256
Cur PV 2
Act PV 2
VG Size 1.94 GB
PE Size 4 MB
Total PE 496
Alloc PE / Size 0 / 0
Free PE / Size 496 / 1.94 GB
VG UUID 3keDZ8-jgky-uhKS-q1bi-d1Jf-qmsq-hw7GUs
--- Volume group ---
VG Name volRaid5
VG Access read/write
VG Status available/resizable
VG # 4
MAX LV 256
Cur LV 0
Open LV 0
MAX LV Size 255.99 GB
Max PV 256
Cur PV 2
Act PV 2
VG Size 3.89 GB
PE Size 4 MB
Total PE 996
Alloc PE / Size 0 / 0
Free PE / Size 996 / 3.89 GB
VG UUID U2l1OW-L3ha-r3kH-BPXw-IJP5-ksA7-77iRJB
--- Volume group ---
VG Name volDisk
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 256
Cur LV 0
Open LV 0
MAX LV Size 255.99 GB
Max PV 256
Cur PV 3
Act PV 3
VG Size 2.91 GB
PE Size 4 MB
Total PE 745
Alloc PE / Size 0 / 0
Free PE / Size 745 / 2.91 GB
VG UUID 7RhXUS-Pw5B-EBYN-GKIM-PO1d-4uD7-4apSvp
--- Volume group ---
VG Name volDisk2
VG Access read/write
VG Status available/resizable
VG # 1
MAX LV 256
Cur LV 0
Open LV 0
MAX LV Size 255.99 GB
Max PV 256
Cur PV 3
Act PV 3
VG Size 2.91 GB
PE Size 4 MB
Total PE 745
Alloc PE / Size 0 / 0
Free PE / Size 745 / 2.91 GB
VG UUID VT6shD-P4lh-Rk2g-DUHi-T2ch-p14Q-kl3BuV
[-- Attachment #2: Type: text/html, Size: 13142 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Error on lvcreate or lvremove!
2002-05-21 16:48 [linux-lvm] Error on lvcreate or lvremove! bo
@ 2002-05-22 7:50 ` Heinz J . Mauelshagen
2002-05-22 21:51 ` bo
0 siblings, 1 reply; 8+ messages in thread
From: Heinz J . Mauelshagen @ 2002-05-22 7:50 UTC (permalink / raw)
To: linux-lvm
On Tue, May 21, 2002 at 02:46:22PM -0700, bo wrote:
> Hello,
>
> I did not have this kind of problem before but I installed LVM1.1-rc2,
> I am experiencing the following errors;
>
> Problem1) could not create an LV from RAID1 vol group
> [root@localhost /]# lvcreate -l 496 -n lvraid1 volRaid1
> lvcreate -- ERROR "Operation not permitted" opening logical volume "/dev/volRaid1/lvraid1"
Looks like your logical volume numbers are invalid.
Take a VGDA backup with vgcfgbackup(8) and store /etc/lvmconf/*
in a safe location.
Run "vgscan -f" and retry.
>
> Problem2) I could not remove it
> [root@localhost /]# lvremove /dev/volRaid1/lvraid1
> lvremove -- do you really want to remove "/dev/volRaid1/lvraid1"? [y/n]: y
> lvremove -- ERROR "lv_release(): LV number" releasing logical volume "/dev/volRaid1/lvraid1"
>
> Problem3) I could not create a striped LV
> [root@localhost /]# lvcreate -l200 -i2 -I4 -n lvjb2s volDisk2
> lvcreate -- not enough allocatable/free physical volume space in "volDisk2"
> lvcreate -- please check, if physical volumes are allocatable
Could be caused by the assumed logical volume number problem but please
check that your physical volumes are allocatable with pvdisplay(8).
Regards,
Heinz -- The LVM Guy --
>
> Attched are more system information.
>
> Please provide me your help,
>
> Thanks,
>
> Bo
>
> [root@localhost /]# pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE PV "/dev/md0" of VG "volRaid0" [1.95 GB / 1.95 GB free]
> pvscan -- ACTIVE PV "/dev/md1" of VG "volRaid0" [1.95 GB / 1.95 GB free]
> pvscan -- ACTIVE PV "/dev/md2" of VG "volRaid0" [1.95 GB / 1.95 GB free]
> pvscan -- ACTIVE PV "/dev/md3" of VG "volRaid1" [992 MB / 992 MB free]
> pvscan -- ACTIVE PV "/dev/md4" of VG "volRaid1" [992 MB / 992 MB free]
> pvscan -- ACTIVE PV "/dev/md5" of VG "volRaid5" [1.95 GB / 1.95 GB free]
> pvscan -- ACTIVE PV "/dev/md6" of VG "volRaid5" [1.95 GB / 1.95 GB free]
> pvscan -- ACTIVE PV "/dev/hdc9" of VG "volDisk" [992 MB / 992 MB free]
> pvscan -- ACTIVE PV "/dev/hdc10" of VG "volDisk2" [992 MB / 992 MB free]
> pvscan -- ACTIVE PV "/dev/hdd9" of VG "volDisk" [992 MB / 992 MB free]
> pvscan -- ACTIVE PV "/dev/hdd10" of VG "volDisk2" [992 MB / 992 MB free]
> pvscan -- ACTIVE PV "/dev/hda15" of VG "volDisk" [996 MB / 996 MB free]
> pvscan -- ACTIVE PV "/dev/hda16" of VG "volDisk2" [996 MB / 996 MB free]
> pvscan -- total: 13 [17.59 GB] / in use: 13 [17.59 GB] / in no VG: 0 [0]
>
> [root@localhost /]# vgdisplay
> --- Volume group ---
> VG Name volRaid0
> VG Access read/write
> VG Status available/resizable
> VG # 2
> MAX LV 256
> Cur LV 0
> Open LV 0
> MAX LV Size 255.99 GB
> Max PV 256
> Cur PV 3
> Act PV 3
> VG Size 5.84 GB
> PE Size 4 MB
> Total PE 1496
> Alloc PE / Size 0 / 0
> Free PE / Size 1496 / 5.84 GB
> VG UUID 89ZFBj-yaQ0-c26m-uKgF-YhvG-2lGR-C8cvWm
>
> --- Volume group ---
> VG Name volRaid1
> VG Access read/write
> VG Status available/resizable
> VG # 3
> MAX LV 256
> Cur LV 0
> Open LV 0
> MAX LV Size 255.99 GB
> Max PV 256
> Cur PV 2
> Act PV 2
> VG Size 1.94 GB
> PE Size 4 MB
> Total PE 496
> Alloc PE / Size 0 / 0
> Free PE / Size 496 / 1.94 GB
> VG UUID 3keDZ8-jgky-uhKS-q1bi-d1Jf-qmsq-hw7GUs
>
> --- Volume group ---
> VG Name volRaid5
> VG Access read/write
> VG Status available/resizable
> VG # 4
> MAX LV 256
> Cur LV 0
> Open LV 0
> MAX LV Size 255.99 GB
> Max PV 256
> Cur PV 2
> Act PV 2
> VG Size 3.89 GB
> PE Size 4 MB
> Total PE 996
> Alloc PE / Size 0 / 0
> Free PE / Size 996 / 3.89 GB
> VG UUID U2l1OW-L3ha-r3kH-BPXw-IJP5-ksA7-77iRJB
>
> --- Volume group ---
> VG Name volDisk
> VG Access read/write
> VG Status available/resizable
> VG # 0
> MAX LV 256
> Cur LV 0
> Open LV 0
> MAX LV Size 255.99 GB
> Max PV 256
> Cur PV 3
> Act PV 3
> VG Size 2.91 GB
> PE Size 4 MB
> Total PE 745
> Alloc PE / Size 0 / 0
> Free PE / Size 745 / 2.91 GB
> VG UUID 7RhXUS-Pw5B-EBYN-GKIM-PO1d-4uD7-4apSvp
>
> --- Volume group ---
> VG Name volDisk2
> VG Access read/write
> VG Status available/resizable
> VG # 1
> MAX LV 256
> Cur LV 0
> Open LV 0
> MAX LV Size 255.99 GB
> Max PV 256
> Cur PV 3
> Act PV 3
> VG Size 2.91 GB
> PE Size 4 MB
> Total PE 745
> Alloc PE / Size 0 / 0
> Free PE / Size 745 / 2.91 GB
> VG UUID VT6shD-P4lh-Rk2g-DUHi-T2ch-p14Q-kl3BuV
>
>
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Error on lvcreate or lvremove!
2002-05-22 7:50 ` Heinz J . Mauelshagen
@ 2002-05-22 21:51 ` bo
2002-05-23 12:04 ` Heinz J . Mauelshagen
0 siblings, 1 reply; 8+ messages in thread
From: bo @ 2002-05-22 21:51 UTC (permalink / raw)
To: linux-lvm
Heinz,
Thanks for your help, it worked.
However, I do not understand why I had this problem and how your suggestion
make
it work. The logical volume number is managed by LVM functions.
Another question is
I have the same problem as mentioned in "Poul Petesen's LVM1.04 pvmove is
broken" email
today as
4) The RedHat 7.2 call to vgscan in rc.sysinit happens before
mounting other file-systems, for example "/usr". This causes the
1.1-rc2
vgscan to fail since libreadline is in /usr/lib.
I did not have this problem on LVM1.0.x. Now, I need to enable LVM and mount
all of these volumes after system boot manually.
Any suggestion or fixes?
Thanks,
Bo
----- Original Message -----
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: <linux-lvm@sistina.com>
Sent: Wednesday, May 22, 2002 5:46 AM
Subject: Re: [linux-lvm] Error on lvcreate or lvremove!
> On Tue, May 21, 2002 at 02:46:22PM -0700, bo wrote:
> > Hello,
> >
> > I did not have this kind of problem before but I installed LVM1.1-rc2,
> > I am experiencing the following errors;
> >
> > Problem1) could not create an LV from RAID1 vol group
> > [root@localhost /]# lvcreate -l 496 -n lvraid1 volRaid1
> > lvcreate -- ERROR "Operation not permitted" opening logical volume
"/dev/volRaid1/lvraid1"
>
> Looks like your logical volume numbers are invalid.
>
> Take a VGDA backup with vgcfgbackup(8) and store /etc/lvmconf/*
> in a safe location.
>
> Run "vgscan -f" and retry.
>
> >
> > Problem2) I could not remove it
> > [root@localhost /]# lvremove /dev/volRaid1/lvraid1
> > lvremove -- do you really want to remove "/dev/volRaid1/lvraid1"?
[y/n]: y
> > lvremove -- ERROR "lv_release(): LV number" releasing logical volume
"/dev/volRaid1/lvraid1"
> >
> > Problem3) I could not create a striped LV
> > [root@localhost /]# lvcreate -l200 -i2 -I4 -n lvjb2s volDisk2
> > lvcreate -- not enough allocatable/free physical volume space in
"volDisk2"
> > lvcreate -- please check, if physical volumes are allocatable
>
> Could be caused by the assumed logical volume number problem but please
> check that your physical volumes are allocatable with pvdisplay(8).
>
> Regards,
> Heinz -- The LVM Guy --
>
>
> >
> > Attched are more system information.
> >
> > Please provide me your help,
> >
> > Thanks,
> >
> > Bo
> >
> > [root@localhost /]# pvscan
> > pvscan -- reading all physical volumes (this may take a while...)
> > pvscan -- ACTIVE PV "/dev/md0" of VG "volRaid0" [1.95 GB / 1.95 GB
free]
> > pvscan -- ACTIVE PV "/dev/md1" of VG "volRaid0" [1.95 GB / 1.95 GB
free]
> > pvscan -- ACTIVE PV "/dev/md2" of VG "volRaid0" [1.95 GB / 1.95 GB
free]
> > pvscan -- ACTIVE PV "/dev/md3" of VG "volRaid1" [992 MB / 992 MB
free]
> > pvscan -- ACTIVE PV "/dev/md4" of VG "volRaid1" [992 MB / 992 MB
free]
> > pvscan -- ACTIVE PV "/dev/md5" of VG "volRaid5" [1.95 GB / 1.95 GB
free]
> > pvscan -- ACTIVE PV "/dev/md6" of VG "volRaid5" [1.95 GB / 1.95 GB
free]
> > pvscan -- ACTIVE PV "/dev/hdc9" of VG "volDisk" [992 MB / 992 MB
free]
> > pvscan -- ACTIVE PV "/dev/hdc10" of VG "volDisk2" [992 MB / 992 MB
free]
> > pvscan -- ACTIVE PV "/dev/hdd9" of VG "volDisk" [992 MB / 992 MB
free]
> > pvscan -- ACTIVE PV "/dev/hdd10" of VG "volDisk2" [992 MB / 992 MB
free]
> > pvscan -- ACTIVE PV "/dev/hda15" of VG "volDisk" [996 MB / 996 MB
free]
> > pvscan -- ACTIVE PV "/dev/hda16" of VG "volDisk2" [996 MB / 996 MB
free]
> > pvscan -- total: 13 [17.59 GB] / in use: 13 [17.59 GB] / in no VG: 0 [0]
> >
> > [root@localhost /]# vgdisplay
> > --- Volume group ---
> > VG Name volRaid0
> > VG Access read/write
> > VG Status available/resizable
> > VG # 2
> > MAX LV 256
> > Cur LV 0
> > Open LV 0
> > MAX LV Size 255.99 GB
> > Max PV 256
> > Cur PV 3
> > Act PV 3
> > VG Size 5.84 GB
> > PE Size 4 MB
> > Total PE 1496
> > Alloc PE / Size 0 / 0
> > Free PE / Size 1496 / 5.84 GB
> > VG UUID 89ZFBj-yaQ0-c26m-uKgF-YhvG-2lGR-C8cvWm
> >
> > --- Volume group ---
> > VG Name volRaid1
> > VG Access read/write
> > VG Status available/resizable
> > VG # 3
> > MAX LV 256
> > Cur LV 0
> > Open LV 0
> > MAX LV Size 255.99 GB
> > Max PV 256
> > Cur PV 2
> > Act PV 2
> > VG Size 1.94 GB
> > PE Size 4 MB
> > Total PE 496
> > Alloc PE / Size 0 / 0
> > Free PE / Size 496 / 1.94 GB
> > VG UUID 3keDZ8-jgky-uhKS-q1bi-d1Jf-qmsq-hw7GUs
> >
> > --- Volume group ---
> > VG Name volRaid5
> > VG Access read/write
> > VG Status available/resizable
> > VG # 4
> > MAX LV 256
> > Cur LV 0
> > Open LV 0
> > MAX LV Size 255.99 GB
> > Max PV 256
> > Cur PV 2
> > Act PV 2
> > VG Size 3.89 GB
> > PE Size 4 MB
> > Total PE 996
> > Alloc PE / Size 0 / 0
> > Free PE / Size 996 / 3.89 GB
> > VG UUID U2l1OW-L3ha-r3kH-BPXw-IJP5-ksA7-77iRJB
> >
> > --- Volume group ---
> > VG Name volDisk
> > VG Access read/write
> > VG Status available/resizable
> > VG # 0
> > MAX LV 256
> > Cur LV 0
> > Open LV 0
> > MAX LV Size 255.99 GB
> > Max PV 256
> > Cur PV 3
> > Act PV 3
> > VG Size 2.91 GB
> > PE Size 4 MB
> > Total PE 745
> > Alloc PE / Size 0 / 0
> > Free PE / Size 745 / 2.91 GB
> > VG UUID 7RhXUS-Pw5B-EBYN-GKIM-PO1d-4uD7-4apSvp
> >
> > --- Volume group ---
> > VG Name volDisk2
> > VG Access read/write
> > VG Status available/resizable
> > VG # 1
> > MAX LV 256
> > Cur LV 0
> > Open LV 0
> > MAX LV Size 255.99 GB
> > Max PV 256
> > Cur PV 3
> > Act PV 3
> > VG Size 2.91 GB
> > PE Size 4 MB
> > Total PE 745
> > Alloc PE / Size 0 / 0
> > Free PE / Size 745 / 2.91 GB
> > VG UUID VT6shD-P4lh-Rk2g-DUHi-T2ch-p14Q-kl3BuV
> >
> >
>
> *** Software bugs are stupid.
> Nevertheless it needs not so stupid people to solve them ***
>
>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
=-
>
> Heinz Mauelshagen Sistina Software Inc.
> Senior Consultant/Developer Am Sonnenhang 11
> 56242 Marienrachdorf
> Germany
> Mauelshagen@Sistina.com +49 2626 141200
> FAX 924446
>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
=-
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Error on lvcreate or lvremove!
2002-05-22 21:51 ` bo
@ 2002-05-23 12:04 ` Heinz J . Mauelshagen
2002-05-23 22:14 ` [linux-lvm] Error on vgscan & lvremove bo
0 siblings, 1 reply; 8+ messages in thread
From: Heinz J . Mauelshagen @ 2002-05-23 12:04 UTC (permalink / raw)
To: linux-lvm
On Wed, May 22, 2002 at 07:49:49PM -0700, bo wrote:
> Heinz,
>
> Thanks for your help, it worked.
> However, I do not understand why I had this problem and how your suggestion
> make
> it work. The logical volume number is managed by LVM functions.
Right.
These problems occir if volume groups are removed physically in a non-devfs
system *without* exporting them first using vgexport.
Then the /dev entries are still there.
Another example causing this is overwriting all physical volumes of a
volume group (IOW: brute force removal of a volume group).
If that happened before, creating new volume groups and/or logical volumes,
you can end up with multiple links in /dev having the same major minor numbers
causing such behaviour.
If vgexport/vgremove are used successfully instead, that shouldn't occur at all.
A 'workaround' for non-devfs configurations is
ls /dev/*/group | sed 's!/group!!' | xargs rm -r ; vgmknodes
which removes all LVM subdirectories and recreates just the valid ones
with all device specials in.
>
> Another question is
>
> I have the same problem as mentioned in "Poul Petesen's LVM1.04 pvmove is
> broken" email
> today as
> 4) The RedHat 7.2 call to vgscan in rc.sysinit happens before
> mounting other file-systems, for example "/usr". This causes the
> 1.1-rc2
> vgscan to fail since libreadline is in /usr/lib.
In order to work around this obstacle, either create the multiple
executable version by running "./configure --disable-single_exec"
(which doesn't use readline)
- or -
link the single executable statically by running
"./configure --enable-static_link" (which doesn't use the shared libs).
Regards,
Heinz -- The LVM Guy --
> I did not have this problem on LVM1.0.x. Now, I need to enable LVM and mount
> all of these volumes after system boot manually.
>
> Any suggestion or fixes?
>
> Thanks,
>
> Bo
>
> ----- Original Message -----
> From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
> To: <linux-lvm@sistina.com>
> Sent: Wednesday, May 22, 2002 5:46 AM
> Subject: Re: [linux-lvm] Error on lvcreate or lvremove!
>
>
> > On Tue, May 21, 2002 at 02:46:22PM -0700, bo wrote:
> > > Hello,
> > >
> > > I did not have this kind of problem before but I installed LVM1.1-rc2,
> > > I am experiencing the following errors;
> > >
> > > Problem1) could not create an LV from RAID1 vol group
> > > [root@localhost /]# lvcreate -l 496 -n lvraid1 volRaid1
> > > lvcreate -- ERROR "Operation not permitted" opening logical volume
> "/dev/volRaid1/lvraid1"
> >
> > Looks like your logical volume numbers are invalid.
> >
> > Take a VGDA backup with vgcfgbackup(8) and store /etc/lvmconf/*
> > in a safe location.
> >
> > Run "vgscan -f" and retry.
> >
> > >
> > > Problem2) I could not remove it
> > > [root@localhost /]# lvremove /dev/volRaid1/lvraid1
> > > lvremove -- do you really want to remove "/dev/volRaid1/lvraid1"?
> [y/n]: y
> > > lvremove -- ERROR "lv_release(): LV number" releasing logical volume
> "/dev/volRaid1/lvraid1"
> > >
> > > Problem3) I could not create a striped LV
> > > [root@localhost /]# lvcreate -l200 -i2 -I4 -n lvjb2s volDisk2
> > > lvcreate -- not enough allocatable/free physical volume space in
> "volDisk2"
> > > lvcreate -- please check, if physical volumes are allocatable
> >
> > Could be caused by the assumed logical volume number problem but please
> > check that your physical volumes are allocatable with pvdisplay(8).
> >
> > Regards,
> > Heinz -- The LVM Guy --
> >
> >
> > >
> > > Attched are more system information.
> > >
> > > Please provide me your help,
> > >
> > > Thanks,
> > >
> > > Bo
> > >
> > > [root@localhost /]# pvscan
> > > pvscan -- reading all physical volumes (this may take a while...)
> > > pvscan -- ACTIVE PV "/dev/md0" of VG "volRaid0" [1.95 GB / 1.95 GB
> free]
> > > pvscan -- ACTIVE PV "/dev/md1" of VG "volRaid0" [1.95 GB / 1.95 GB
> free]
> > > pvscan -- ACTIVE PV "/dev/md2" of VG "volRaid0" [1.95 GB / 1.95 GB
> free]
> > > pvscan -- ACTIVE PV "/dev/md3" of VG "volRaid1" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/md4" of VG "volRaid1" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/md5" of VG "volRaid5" [1.95 GB / 1.95 GB
> free]
> > > pvscan -- ACTIVE PV "/dev/md6" of VG "volRaid5" [1.95 GB / 1.95 GB
> free]
> > > pvscan -- ACTIVE PV "/dev/hdc9" of VG "volDisk" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/hdc10" of VG "volDisk2" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/hdd9" of VG "volDisk" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/hdd10" of VG "volDisk2" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/hda15" of VG "volDisk" [996 MB / 996 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/hda16" of VG "volDisk2" [996 MB / 996 MB
> free]
> > > pvscan -- total: 13 [17.59 GB] / in use: 13 [17.59 GB] / in no VG: 0 [0]
> > >
> > > [root@localhost /]# vgdisplay
> > > --- Volume group ---
> > > VG Name volRaid0
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 2
> > > MAX LV 256
> > > Cur LV 0
> > > Open LV 0
> > > MAX LV Size 255.99 GB
> > > Max PV 256
> > > Cur PV 3
> > > Act PV 3
> > > VG Size 5.84 GB
> > > PE Size 4 MB
> > > Total PE 1496
> > > Alloc PE / Size 0 / 0
> > > Free PE / Size 1496 / 5.84 GB
> > > VG UUID 89ZFBj-yaQ0-c26m-uKgF-YhvG-2lGR-C8cvWm
> > >
> > > --- Volume group ---
> > > VG Name volRaid1
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 3
> > > MAX LV 256
> > > Cur LV 0
> > > Open LV 0
> > > MAX LV Size 255.99 GB
> > > Max PV 256
> > > Cur PV 2
> > > Act PV 2
> > > VG Size 1.94 GB
> > > PE Size 4 MB
> > > Total PE 496
> > > Alloc PE / Size 0 / 0
> > > Free PE / Size 496 / 1.94 GB
> > > VG UUID 3keDZ8-jgky-uhKS-q1bi-d1Jf-qmsq-hw7GUs
> > >
> > > --- Volume group ---
> > > VG Name volRaid5
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 4
> > > MAX LV 256
> > > Cur LV 0
> > > Open LV 0
> > > MAX LV Size 255.99 GB
> > > Max PV 256
> > > Cur PV 2
> > > Act PV 2
> > > VG Size 3.89 GB
> > > PE Size 4 MB
> > > Total PE 996
> > > Alloc PE / Size 0 / 0
> > > Free PE / Size 996 / 3.89 GB
> > > VG UUID U2l1OW-L3ha-r3kH-BPXw-IJP5-ksA7-77iRJB
> > >
> > > --- Volume group ---
> > > VG Name volDisk
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 0
> > > MAX LV 256
> > > Cur LV 0
> > > Open LV 0
> > > MAX LV Size 255.99 GB
> > > Max PV 256
> > > Cur PV 3
> > > Act PV 3
> > > VG Size 2.91 GB
> > > PE Size 4 MB
> > > Total PE 745
> > > Alloc PE / Size 0 / 0
> > > Free PE / Size 745 / 2.91 GB
> > > VG UUID 7RhXUS-Pw5B-EBYN-GKIM-PO1d-4uD7-4apSvp
> > >
> > > --- Volume group ---
> > > VG Name volDisk2
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 1
> > > MAX LV 256
> > > Cur LV 0
> > > Open LV 0
> > > MAX LV Size 255.99 GB
> > > Max PV 256
> > > Cur PV 3
> > > Act PV 3
> > > VG Size 2.91 GB
> > > PE Size 4 MB
> > > Total PE 745
> > > Alloc PE / Size 0 / 0
> > > Free PE / Size 745 / 2.91 GB
> > > VG UUID VT6shD-P4lh-Rk2g-DUHi-T2ch-p14Q-kl3BuV
> > >
> > >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
> >
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Error on vgscan & lvremove
2002-05-23 12:04 ` Heinz J . Mauelshagen
@ 2002-05-23 22:14 ` bo
2002-05-24 4:01 ` Heinz J . Mauelshagen
0 siblings, 1 reply; 8+ messages in thread
From: bo @ 2002-05-23 22:14 UTC (permalink / raw)
To: linux-lvm
Heinz,
> A 'workaround' for non-devfs configurations is
>
> ls /dev/*/group | sed 's!/group!!' | xargs rm -r ; vgmknodes
>
??Something wrong on "sed 's!/group!!' ", it did not work.
>
> link the single executable statically by running
> "./configure --enable-static_link" (which doesn't use the shared libs).
>
It did not work. I rebuilt LINUX kernel & LVM after
"./configure --enable-static_link".
I got the same result.
Another big issues came as follow;
I tried to go back to LVM1.0.3, but getting a big trouble.
Q1: Is it backward compatible from LVM1.1-rc2 to LVM1.0.3 or not?
I already built the volume from LVM1.1-rc2 then I went back to
LVM1.0.3.
All of LVM tools are not working as shown in the following console
output.
Q2: How could I remove this volume and rebuild? I do not care about the
data.
During boot or after the boot, I have the following errors;
[root@localhost /]# vgscan -f
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found inactive volume group "volRaid0"
vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volRaid0"
is inconsistent
vgscan -- ERROR: unable to do a backup of volume group "volRaid0"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
"volRaid0" from "/etc/lvmtab"
vgscan -- found inactive volume group "volRaid5"
vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volRaid5"
is inconsistent
vgscan -- ERROR: unable to do a backup of volume group "volRaid5"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
"volRaid5" from "/etc/lvmtab"
vgscan -- found inactive volume group "volDisk"
vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volDisk"
is inconsistent
vgscan -- ERROR: unable to do a backup of volume group "volDisk"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
"volDisk" from "/etc/lvmtab"
vgscan -- found inactive volume group "volDisk2"
vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volDisk2"
is inconsistent
vgscan -- ERROR: unable to do a backup of volume group "volDisk2"
vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
"volDisk2" from "/etc/lvmtab"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume
groups
[root@localhost /root]# ls /dev/*/group
ls: /dev/*/group: No such file or directory
[root@localhost /root]# vgmknodes
vgmknodes -- no volume groups found to create nodes for
Thanks for your help,
Bo
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Error on vgscan & lvremove
2002-05-23 22:14 ` [linux-lvm] Error on vgscan & lvremove bo
@ 2002-05-24 4:01 ` Heinz J . Mauelshagen
2002-05-24 16:34 ` bo
0 siblings, 1 reply; 8+ messages in thread
From: Heinz J . Mauelshagen @ 2002-05-24 4:01 UTC (permalink / raw)
To: linux-lvm
On Thu, May 23, 2002 at 08:12:04PM -0700, bo wrote:
> Heinz,
>
> > A 'workaround' for non-devfs configurations is
> >
> > ls /dev/*/group | sed 's!/group!!' | xargs rm -r ; vgmknodes
> >
>
> ??Something wrong on "sed 's!/group!!' ", it did not work.
Works fine here. Maybe your sed doesn't like the delimiter?
Try '/' rather than '!' with sed like "sed 's/\/group//'".
>
> >
> > link the single executable statically by running
> > "./configure --enable-static_link" (which doesn't use the shared libs).
> >
>
> It did not work. I rebuilt LINUX kernel & LVM after
> "./configure --enable-static_link".
> I got the same result.
Did you start with a fresh source tree or run "make distclean"
before "./configure --enable-static_link"?
>
> Another big issues came as follow;
>
> I tried to go back to LVM1.0.3, but getting a big trouble.
>
> Q1: Is it backward compatible from LVM1.1-rc2 to LVM1.0.3 or not?
>
> I already built the volume from LVM1.1-rc2 then I went back to
> LVM1.0.3.
> All of LVM tools are not working as shown in the following console
> output.
>
> Q2: How could I remove this volume and rebuild? I do not care about the
> data.
No LV status flags have been changed at all in 1.1-rc.
lv_check_consistency() checks for the 2 possible user land states in lv_status
which are either 0 or LV_ACTIVE.
For fast progress it should be ok to remove the lv_status checks from
lv_check_consistency().
For further investigation of a possible 1.1-rc flaw ITR, could you send
me (mge@sistina.com) the output files created with
for d in All_volRaid0_PVs
do
dd if=/dev/YOurPV of=`basename $d`.vgda bs=1k count=4
done
packed into a compressed tar archive?
Thanks,
Heinz -- The LVM Guy --
>
> During boot or after the boot, I have the following errors;
>
> [root@localhost /]# vgscan -f
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found inactive volume group "volRaid0"
> vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volRaid0"
> is inconsistent
> vgscan -- ERROR: unable to do a backup of volume group "volRaid0"
> vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
> "volRaid0" from "/etc/lvmtab"
> vgscan -- found inactive volume group "volRaid5"
> vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volRaid5"
> is inconsistent
> vgscan -- ERROR: unable to do a backup of volume group "volRaid5"
> vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
> "volRaid5" from "/etc/lvmtab"
> vgscan -- found inactive volume group "volDisk"
> vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volDisk"
> is inconsistent
> vgscan -- ERROR: unable to do a backup of volume group "volDisk"
> vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
> "volDisk" from "/etc/lvmtab"
> vgscan -- found inactive volume group "volDisk2"
> vgscan -- ERROR "lv_check_consistency(): LV status" volume group "volDisk2"
> is inconsistent
> vgscan -- ERROR: unable to do a backup of volume group "volDisk2"
> vgscan -- ERROR "lvm_tab_vg_remove(): unlink" removing volume group
> "volDisk2" from "/etc/lvmtab"
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume
> groups
>
> [root@localhost /root]# ls /dev/*/group
> ls: /dev/*/group: No such file or directory
> [root@localhost /root]# vgmknodes
> vgmknodes -- no volume groups found to create nodes for
>
>
> Thanks for your help,
>
> Bo
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Error on vgscan & lvremove
2002-05-24 4:01 ` Heinz J . Mauelshagen
@ 2002-05-24 16:34 ` bo
2002-05-25 5:53 ` Heinz J . Mauelshagen
0 siblings, 1 reply; 8+ messages in thread
From: bo @ 2002-05-24 16:34 UTC (permalink / raw)
To: linux-lvm
Heinz,
I verified these two issues as commented below;
> >
> > > A 'workaround' for non-devfs configurations is
> > >
> > > ls /dev/*/group | sed 's!/group!!' | xargs rm -r ; vgmknodes
> > >
> >
> > ??Something wrong on "sed 's!/group!!' ", it did not work.
>
> Works fine here. Maybe your sed doesn't like the delimiter?
>
> Try '/' rather than '!' with sed like "sed 's/\/group//'".
>
worked w/o delimiters like
ls /dev/*/group | sed 's/group//' | xargs rm -r ; vgmknodes
> >
> > >
> > > link the single executable statically by running
> > > "./configure --enable-static_link" (which doesn't use the shared
libs).
> > >
> >
> > It did not work. I rebuilt LINUX kernel & LVM after
> > "./configure --enable-static_link".
> > I got the same result.
>
> Did you start with a fresh source tree or run "make distclean"
> before "./configure --enable-static_link"?
>
> >
Yes, worked with "make distclean".
For the backward compatibilty I will try later.
One more question related with activating PV,
Of course I could make them active after removing the volume and recreating
it.
As you can notice on the attached log VG is ok, How could I make these PVs
active
w/o removing the volume?
Did it corrupt the VGDA? any way to recover it?
(PS: you can notice TWO "volDisk" group in the following "vgdisplay", should
be
volDisk & volDisk2 ???)
Thanks again,
Bo
----------------------------------------------------------------------------
-----------------
[root@localhost /root]# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE PV "/dev/md0" of VG "volRaid0" [1.95 GB / 0 free]
pvscan -- ACTIVE PV "/dev/md1" of VG "volRaid0" [1.95 GB / 0 free]
pvscan -- ACTIVE PV "/dev/md2" of VG "volRaid0" [1.95 GB / 0 free]
pvscan -- ACTIVE PV "/dev/md3" of VG "volRaid1" [992 MB / 0 free]
pvscan -- ACTIVE PV "/dev/md4" of VG "volRaid1" [992 MB / 484 MB free]
pvscan -- ACTIVE PV "/dev/md5" of VG "volRaid5" [1.95 GB / 992 MB free]
pvscan -- ACTIVE PV "/dev/md6" of VG "volRaid5" [1.95 GB / 1.95 GB free]
pvscan -- ACTIVE PV "/dev/hdc9" of VG "volDisk" [992 MB / 992 MB free]
pvscan -- inactive PV "/dev/hdc10" of VG "volDisk2" [992 MB / 788 MB free]
pvscan -- ACTIVE PV "/dev/hdd9" of VG "volDisk" [992 MB / 992 MB free]
pvscan -- inactive PV "/dev/hdd10" of VG "volDisk2" [992 MB / 792 MB free]
pvscan -- ACTIVE PV "/dev/hda15" of VG "volDisk" [996 MB / 996 MB free]
pvscan -- inactive PV "/dev/hda16" of VG "volDisk2" [996 MB / 0 free]
pvscan -- total: 13 [17.59 GB] / in use: 13 [17.59 GB] / in no VG: 0 [0]
[root@localhost /root]# pvdisplay /dev/hdc10
--- Physical volume ---
PV Name /dev/hdc10
VG Name volDisk2
PV Size 1000.09 MB [2048193 secs] / NOT usable 4.19 MB [LVM:
128 KB]
PV# 2
PV Status available
Allocatable yes
Cur LV 2
PE Size (KByte) 4096
Total PE 248
Free PE 197
Allocated PE 51
PV UUID b5ybET-1zOq-HPnP-QQda-zjgQ-5avz-aGFMav
[root@localhost /root]# vgdisplay
--- Volume group ---
VG Name volDisk
VG Access read/write
VG Status available/resizable
VG # 1
MAX LV 256
Cur LV 0
Open LV 0
MAX LV Size 255.99 GB
Max PV 256
Cur PV 3
Act PV 3
VG Size 2.91 GB
PE Size 4 MB
Total PE 745
Alloc PE / Size 0 / 0
Free PE / Size 745 / 2.91 GB
VG UUID 7RhXUS-Pw5B-EBYN-GKIM-PO1d-4uD7-4apSvp
--- Volume group ---
VG Name volDisk
VG Access read/write
VG Status available/resizable
VG # 1
MAX LV 256
Cur LV 0
Open LV 0
MAX LV Size 255.99 GB
Max PV 256
Cur PV 3
Act PV 3
VG Size 2.91 GB
PE Size 4 MB
Total PE 745
Alloc PE / Size 0 / 0
Free PE / Size 745 / 2.91 GB
VG UUID 7RhXUS-Pw5B-EBYN-GKIM-PO1d-4uD7-4apSvp
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Error on vgscan & lvremove
2002-05-24 16:34 ` bo
@ 2002-05-25 5:53 ` Heinz J . Mauelshagen
0 siblings, 0 replies; 8+ messages in thread
From: Heinz J . Mauelshagen @ 2002-05-25 5:53 UTC (permalink / raw)
To: linux-lvm
On Fri, May 24, 2002 at 02:32:19PM -0700, bo wrote:
> Heinz,
>
> I verified these two issues as commented below;
>
> > >
> > > > A 'workaround' for non-devfs configurations is
> > > >
> > > > ls /dev/*/group | sed 's!/group!!' | xargs rm -r ; vgmknodes
> > > >
> > >
> > > ??Something wrong on "sed 's!/group!!' ", it did not work.
> >
> > Works fine here. Maybe your sed doesn't like the delimiter?
> >
> > Try '/' rather than '!' with sed like "sed 's/\/group//'".
> >
>
> worked w/o delimiters like
>
> ls /dev/*/group | sed 's/group//' | xargs rm -r ; vgmknodes
Yes, trailing / doesn't matter in the rm args :)
>
> > >
> > > >
> > > > link the single executable statically by running
> > > > "./configure --enable-static_link" (which doesn't use the shared
> libs).
> > > >
> > >
> > > It did not work. I rebuilt LINUX kernel & LVM after
> > > "./configure --enable-static_link".
> > > I got the same result.
> >
> > Did you start with a fresh source tree or run "make distclean"
> > before "./configure --enable-static_link"?
> >
> > >
>
> Yes, worked with "make distclean".
Good.
>
> For the backward compatibilty I will try later.
OK.
>
> One more question related with activating PV,
>
> Of course I could make them active after removing the volume and recreating
> it.
> As you can notice on the attached log VG is ok, How could I make these PVs
> active
> w/o removing the volume?
>
> Did it corrupt the VGDA? any way to recover it?
See below.
> (PS: you can notice TWO "volDisk" group in the following "vgdisplay", should
> be
> volDisk & volDisk2 ???)
You still seem to have wrong /dev/ entries :-(
Maybe because of earlier problems, 2 VGs (volDisk and volDisk2) now
have the same internal number?
Please send the output of
"pvdata -a /dev/hd[cd]9 /dev/hda15 /dev/hd[cd]10 /dev/hda16 ; ls -lR /dev"
directly to me (mge@sistina.com).
If volDisk and VolDisk2 have the same internal numbers, we can try "vgscan -f"
which comes with LVM >= 1.0.3.
Regards,
Heinz -- The LVM Guy --
>
> Thanks again,
>
> Bo
> ----------------------------------------------------------------------------
> -----------------
> [root@localhost /root]# pvscan
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE PV "/dev/md0" of VG "volRaid0" [1.95 GB / 0 free]
> pvscan -- ACTIVE PV "/dev/md1" of VG "volRaid0" [1.95 GB / 0 free]
> pvscan -- ACTIVE PV "/dev/md2" of VG "volRaid0" [1.95 GB / 0 free]
> pvscan -- ACTIVE PV "/dev/md3" of VG "volRaid1" [992 MB / 0 free]
> pvscan -- ACTIVE PV "/dev/md4" of VG "volRaid1" [992 MB / 484 MB free]
> pvscan -- ACTIVE PV "/dev/md5" of VG "volRaid5" [1.95 GB / 992 MB free]
> pvscan -- ACTIVE PV "/dev/md6" of VG "volRaid5" [1.95 GB / 1.95 GB free]
> pvscan -- ACTIVE PV "/dev/hdc9" of VG "volDisk" [992 MB / 992 MB free]
> pvscan -- inactive PV "/dev/hdc10" of VG "volDisk2" [992 MB / 788 MB free]
> pvscan -- ACTIVE PV "/dev/hdd9" of VG "volDisk" [992 MB / 992 MB free]
> pvscan -- inactive PV "/dev/hdd10" of VG "volDisk2" [992 MB / 792 MB free]
> pvscan -- ACTIVE PV "/dev/hda15" of VG "volDisk" [996 MB / 996 MB free]
> pvscan -- inactive PV "/dev/hda16" of VG "volDisk2" [996 MB / 0 free]
> pvscan -- total: 13 [17.59 GB] / in use: 13 [17.59 GB] / in no VG: 0 [0]
>
> [root@localhost /root]# pvdisplay /dev/hdc10
> --- Physical volume ---
> PV Name /dev/hdc10
> VG Name volDisk2
> PV Size 1000.09 MB [2048193 secs] / NOT usable 4.19 MB [LVM:
> 128 KB]
> PV# 2
> PV Status available
> Allocatable yes
> Cur LV 2
> PE Size (KByte) 4096
> Total PE 248
> Free PE 197
> Allocated PE 51
> PV UUID b5ybET-1zOq-HPnP-QQda-zjgQ-5avz-aGFMav
>
> [root@localhost /root]# vgdisplay
> --- Volume group ---
> VG Name volDisk
> VG Access read/write
> VG Status available/resizable
> VG # 1
> MAX LV 256
> Cur LV 0
> Open LV 0
> MAX LV Size 255.99 GB
> Max PV 256
> Cur PV 3
> Act PV 3
> VG Size 2.91 GB
> PE Size 4 MB
> Total PE 745
> Alloc PE / Size 0 / 0
> Free PE / Size 745 / 2.91 GB
> VG UUID 7RhXUS-Pw5B-EBYN-GKIM-PO1d-4uD7-4apSvp
>
> --- Volume group ---
> VG Name volDisk
> VG Access read/write
> VG Status available/resizable
> VG # 1
> MAX LV 256
> Cur LV 0
> Open LV 0
> MAX LV Size 255.99 GB
> Max PV 256
> Cur PV 3
> Act PV 3
> VG Size 2.91 GB
> PE Size 4 MB
> Total PE 745
> Alloc PE / Size 0 / 0
> Free PE / Size 745 / 2.91 GB
> VG UUID 7RhXUS-Pw5B-EBYN-GKIM-PO1d-4uD7-4apSvp
>
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2002-05-25 5:53 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-05-21 16:48 [linux-lvm] Error on lvcreate or lvremove! bo
2002-05-22 7:50 ` Heinz J . Mauelshagen
2002-05-22 21:51 ` bo
2002-05-23 12:04 ` Heinz J . Mauelshagen
2002-05-23 22:14 ` [linux-lvm] Error on vgscan & lvremove bo
2002-05-24 4:01 ` Heinz J . Mauelshagen
2002-05-24 16:34 ` bo
2002-05-25 5:53 ` Heinz J . Mauelshagen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox