Skip to contentSkip to conversation

Problem extending a LV

linux-lvm Carsten Balzer 7 participants 8 messages May 29, 2001 – May 30, 2001

lore
Share & tools
lore

Carsten Balzer

author
#0 lore raw

Hi

I have a strange problem with kernel 2.2.19 an lvm-tools 0.9.1_beta7.

I have a existing VG with 2 80GB disks containing one 160GB LV. I added a additional 80GB disk and wanted to extend the LV. But that didn't
work.

seven:/ # pvdisplay /dev/hdf1
--- Physical volume ---

PV Name               /dev/hdf1
VG Name               NVolGroup
PV Size               76.34 GB / NOT usable 3.22 MB [LVM: 306 KB]
PV#                   3
PV Status             available
Allocatable           yes
Cur LV                0
PE Size (KByte)       4096
Total PE              19541
Free PE               19541
Allocated PE          0
PV UUID               o593Dd-Uo4Z-Hv1Z-yTI0-QtYy-p0Wq-a4XL3q

seven:/ # vgdisplay
--- Volume group ---

VG Name               NVolGroup
VG Access             read/write
VG Status             available/resizable
VG #                  0
MAX LV                256
Cur LV                1
Open LV               1
MAX LV Size           255.99 GB
Max PV                256
Cur PV                3
Act PV                3
VG Size               229 GB
PE Size               4 MB
Total PE              58623
Alloc PE / Size       39082 / 152.66 GB
Free  PE / Size       19541 / 76.33 GB
VG UUID               lHyDca-e7yA-4Rkt-keGF-uJHY-YCRk-3qqw7N

seven:/ # lvdisplay /dev/NVolGroup/nVol
--- Logical volume ---

LV Name                /dev/NVolGroup/nVol
VG Name                NVolGroup
LV Write Access        read/write
LV Status              available
LV #                   1
# open                 1
LV Size                152.66 GB
Current LE             39082
Allocated LE           39082
Stripes                2
Stripe size (KByte)    16
Allocation             next free
Read ahead sectors     120
Block device           58:0

If I try to extend the LV with:
lvextend -L+78164M /dev/NVolGroup/nVol
then I get:
lvextend -- rounding size 240119808 KB to stripe boundary size 240123904 KB
lvextend -- only 19541 free physical extents in volume group "NVolGroup"

Next try with: lvextend -l+19541 /dev/NVolGroup/nVol lvextend -- rounding size 240119808 KB to stripe boundary size 240123904 KB
lvextend -- only 19541 free physical extents in volume group "NVolGroup"

Where is the error?

Gru�
Carsten

--
"Who the fuck is General Failure and why is he reading my disk?"

#1 lore raw
Quoted 11 lines · Carsten Balzer

If I try to extend the LV with:
lvextend -L+78164M /dev/NVolGroup/nVol
then I get:
lvextend -- rounding size 240119808 KB to stripe boundary size 240123904 KB
lvextend -- only 19541 free physical extents in volume group "NVolGroup"

Next try with: lvextend -l+19541 /dev/NVolGroup/nVol lvextend -- rounding size 240119808 KB to stripe boundary size 240123904 KB
lvextend -- only 19541 free physical extents in volume group "NVolGroup"

You cannot currently extend a striped LV onto a new disk. It would involve completely rearranging the data to account for the new striping configuration. The reason you get the error is because the tools know this and are trying to extend on the two original PVs. If you want to have the ability to extend the LV onto new disks, you must use linear LVs.

Regards,

Signature · 13 lines
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: [email protected]
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
A bad random number generator: 1, 1, 1, 1, 1, 4.33e+67, 1, 1, 1...
-----End Obligatory Humorous Quote------------------------------------------
#2 lore raw

Are there plans to have this functionality? As in, I have a 2 disk striped set, and now I'm running out of space, so I add a third pv, and now I want to restripe and extend onto the third disk? I ask because Veritas has this ability, and it could be a deal breaker for some choosing which to use.

Signature · 5 lines
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [email protected]
Quoted 28 lines · AJ Lewis
Quoted 4 lines · Carsten Balzer

If I try to extend the LV with:
lvextend -L+78164M /dev/NVolGroup/nVol
then I get:
lvextend -- rounding size 240119808 KB to stripe boundary size

240123904

Quoted 2 lines

KB
lvextend -- only 19541 free physical extents in volume group

"NVolGroup"

Quoted 3 lines

Next try with: lvextend -l+19541 /dev/NVolGroup/nVol lvextend -- rounding size 240119808 KB to stripe boundary size

240123904

Quoted 2 lines

KB
lvextend -- only 19541 free physical extents in volume group

"NVolGroup"

You cannot currently extend a striped LV onto a new disk. It would involve
completely rearranging the data to account for the new striping configuration. The reason you get the error is because the tools know this
and are trying to extend on the two original PVs. If you want to have the
ability to extend the LV onto new disks, you must use linear LVs.

Regards,

#3 lore raw

Hi,

You mention that Veritas (presumably the Volume Manager) has this functionality. Are you sure that you can add a subdisk to a striped plex in a volume? I'm just curious because I can not remember that this is actually possible....

++Jos

And thus it came to pass that Austin Gonyou wrote:
(on Tue, May 29, 2001 at 01:35:07PM -0500 to be exact)

Quoted 48 lines

Are there plans to have this functionality? As in, I have a 2 disk striped set, and now I'm running out of space, so I add a third pv, and now I want to restripe and extend onto the third disk? I ask because Veritas has this ability, and it could be a deal breaker for some choosing which to use.

Signature · 5 lines
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [email protected]
Quoted 26 lines · AJ Lewis
Quoted 4 lines · Carsten Balzer

If I try to extend the LV with:
lvextend -L+78164M /dev/NVolGroup/nVol
then I get:
lvextend -- rounding size 240119808 KB to stripe boundary size

240123904

Quoted 2 lines

KB
lvextend -- only 19541 free physical extents in volume group

"NVolGroup"

Quoted 3 lines

Next try with: lvextend -l+19541 /dev/NVolGroup/nVol lvextend -- rounding size 240119808 KB to stripe boundary size

240123904

Quoted 2 lines

KB
lvextend -- only 19541 free physical extents in volume group

"NVolGroup"

You cannot currently extend a striped LV onto a new disk. It would involve
completely rearranging the data to account for the new striping configuration. The reason you get the error is because the tools know this
and are trying to extend on the two original PVs. If you want to have the
ability to extend the LV onto new disks, you must use linear LVs.

Quoted 2 lines

Regards,

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Signature · 2 lines
If you do what you've always done,
You get what you've always gotten.
#4 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

The HP VxVm (Veritas Volume Mangager for HP-UX 11i) has this
functionality. If you have enough spare space you can also change stripe sizes on the fly too.

Tom.

Quoted 62 lines · [email protected] wrote:

Hi,

You mention that Veritas (presumably the Volume Manager) has this functionality. Are you sure that you can add a subdisk to a striped plex in a volume? I'm just curious because I can not remember that this is actually possible....

++Jos

And thus it came to pass that Austin Gonyou wrote:
(on Tue, May 29, 2001 at 01:35:07PM -0500 to be exact)

Quoted 40 lines

Are there plans to have this functionality? As in, I have a 2 disk striped set, and now I'm running out of space, so I add a third pv, and now I want to restripe and extend onto the third disk? I ask because Veritas has this ability, and it could be a deal breaker for some choosing which to use.

--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [email protected]

Quoted 26 lines · AJ Lewis
Quoted 4 lines · Carsten Balzer

If I try to extend the LV with:
lvextend -L+78164M /dev/NVolGroup/nVol
then I get:
lvextend -- rounding size 240119808 KB to stripe boundary size

240123904

Quoted 2 lines

KB
lvextend -- only 19541 free physical extents in volume group

"NVolGroup"

Quoted 3 lines

Next try with: lvextend -l+19541 /dev/NVolGroup/nVol lvextend -- rounding size 240119808 KB to stripe boundary size

240123904

Quoted 2 lines

KB
lvextend -- only 19541 free physical extents in volume group

"NVolGroup"

You cannot currently extend a striped LV onto a new disk. It would involve
completely rearranging the data to account for the new striping configuration. The reason you get the error is because the tools know this
and are trying to extend on the two original PVs. If you want to have the
ability to extend the LV onto new disks, you must use linear LVs.

Quoted 8 lines
Quoted 2 lines

Regards,

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Quoted 8 lines

--
If you do what you've always done,
You get what you've always gotten.
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

- --
char *t,*n,*i="%.9s%.7s%.7s\n";extern void exit(int);extern int printf(const char *,...);int main(){int v=*i,g,e=*(i-~(v/=v))%*(i+v);g=*i+~e--; t=n=" DISPLAY'tmdg@uksr';,,;'.hp.com'*>"+g;v=g-e; e-=printf(i,n- v,e+n,t); t=n=" DISPLAY'http://www.itrc.hp.com/' *>"-~g;exit(g+~printf(i,n+~v,e+n,t));}

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.1i

iQA/AwUBOxS2RAbfKggmajr3EQKACwCggAwu+r/4Q/xTn0pFiYgNsAMXnoUAoPKC rqG6slFd3xhqXS7oR7vB7pRX
=Pdmj
-----END PGP SIGNATURE-----

#5 lore raw
In reply to [email protected]

Quoting [email protected] <[email protected]>:

Quoted 7 lines

You mention that Veritas (presumably the Volume Manager) has this functionality. Are you sure that you can add a subdisk to a striped plex in a volume? I'm just curious because I can not remember that this is actually possible....

++Jos

Yes, you can add/remove columns(would be a sd in your case) in a striped plex with VxVM.
ex: vxassist -g <dgname> relayout <volname> ncol=5

Signature · 3 lines
Oscar Wahlberg <oscar.wahlberg(at)home.se>
"There are only two industries that refer to their customers 
as 'users'." --Edward Tufte
#6 lore raw
In reply to Austin Gonyou
Quoted 1 line · Austin Gonyou

Are there plans to have this functionality?

Yes, as mentioned in my other related mail.

Quoted 4 lines

As in, I have a 2 disk striped
set, and now I'm running out of space, so I add a third pv, and now I want to restripe and extend onto the third disk? I ask because Veritas has this ability, and it could be a deal breaker for some choosing which to use.

All right, that's one reason why we want to have it. A post 1.0 feature though :-(

Regards,
Heinz -- The LVM Guy --

Quoted 44 lines
Signature · 6 lines
-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [email protected]
Quoted 26 lines · AJ Lewis
Quoted 4 lines · Carsten Balzer

If I try to extend the LV with:
lvextend -L+78164M /dev/NVolGroup/nVol
then I get:
lvextend -- rounding size 240119808 KB to stripe boundary size

240123904

Quoted 2 lines

KB
lvextend -- only 19541 free physical extents in volume group

"NVolGroup"

Quoted 3 lines

Next try with: lvextend -l+19541 /dev/NVolGroup/nVol lvextend -- rounding size 240119808 KB to stripe boundary size

240123904

Quoted 2 lines

KB
lvextend -- only 19541 free physical extents in volume group

"NVolGroup"

You cannot currently extend a striped LV onto a new disk. It would involve
completely rearranging the data to account for the new striping configuration. The reason you get the error is because the tools know this
and are trying to extend on the two original PVs. If you want to have the
ability to extend the LV onto new disks, you must use linear LVs.

Quoted 2 lines

Regards,

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf Germany
[email protected] +49 2626 141200

                                                       FAX 924446

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

#7 lore raw
In reply to Carsten Balzer

Carsten,

sorry, you can't extend a striped LV like this today :-( Will be enhanced in a later release.

Quoted 85 lines · Carsten Balzer

Hi

I have a strange problem with kernel 2.2.19 an lvm-tools 0.9.1_beta7.

I have a existing VG with 2 80GB disks containing one 160GB LV. I added a additional 80GB disk and wanted to extend the LV. But that didn't
work.

seven:/ # pvdisplay /dev/hdf1
--- Physical volume ---

PV Name               /dev/hdf1
VG Name               NVolGroup
PV Size               76.34 GB / NOT usable 3.22 MB [LVM: 306 KB]
PV#                   3
PV Status             available
Allocatable           yes
Cur LV                0
PE Size (KByte)       4096
Total PE              19541
Free PE               19541
Allocated PE          0
PV UUID               o593Dd-Uo4Z-Hv1Z-yTI0-QtYy-p0Wq-a4XL3q

seven:/ # vgdisplay
--- Volume group ---

VG Name               NVolGroup
VG Access             read/write
VG Status             available/resizable
VG #                  0
MAX LV                256
Cur LV                1
Open LV               1
MAX LV Size           255.99 GB
Max PV                256
Cur PV                3
Act PV                3
VG Size               229 GB
PE Size               4 MB
Total PE              58623
Alloc PE / Size       39082 / 152.66 GB
Free  PE / Size       19541 / 76.33 GB
VG UUID               lHyDca-e7yA-4Rkt-keGF-uJHY-YCRk-3qqw7N

seven:/ # lvdisplay /dev/NVolGroup/nVol
--- Logical volume ---

LV Name                /dev/NVolGroup/nVol
VG Name                NVolGroup
LV Write Access        read/write
LV Status              available
LV #                   1
# open                 1
LV Size                152.66 GB
Current LE             39082
Allocated LE           39082
Stripes                2
Stripe size (KByte)    16
Allocation             next free
Read ahead sectors     120
Block device           58:0

If I try to extend the LV with:
lvextend -L+78164M /dev/NVolGroup/nVol
then I get:
lvextend -- rounding size 240119808 KB to stripe boundary size 240123904 KB
lvextend -- only 19541 free physical extents in volume group "NVolGroup"

Next try with: lvextend -l+19541 /dev/NVolGroup/nVol lvextend -- rounding size 240119808 KB to stripe boundary size 240123904 KB
lvextend -- only 19541 free physical extents in volume group "NVolGroup"

Where is the error?

Gru�
Carsten

--
"Who the fuck is General Failure and why is he reading my disk?"
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Signature · 15 lines
Regards,
Heinz    -- The LVM Guy --

*** 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
[email protected]                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-