http://qa.mandrakesoft.com/show_bug.cgi?id=6383
Summary: diskdrake offers too too much space when resizing LVM
volumes
Product: drakxtools
Version: 9.3-5mdk
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: diskdrake
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I have one volume group:
# vgdisplay
--- Volume group ---
VG Name default_volume
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 255
Cur LV 2
Open LV 1
MAX LV Size 255.99 GB
Max PV 255
Cur PV 2
Act PV 2
VG Size 4.98 GB
PE Size 4 MB
Total PE 1276
Alloc PE / Size 1176 / 4.59 GB
Free PE / Size 100 / 400 MB
VG UUID OlTYL1-NxcV-VN6u-AtUC-05T3-8Rut-smYY3F
When resizing this volume:
# lvdisplay /dev/default_volume/2
--- Logical volume ---
LV Name /dev/default_volume/2
VG Name default_volume
LV Write Access read/write
LV Status available
LV # 2
# open 1
LV Size 608 MB
Current LE 152
Allocated LE 152
Allocation next free
Read ahead sectors 1024
Block device 58:1
Diskdrake offers to resize it to up to 5104 MB, even though the unassigned space
on the VG is correctly indicated in diskdrake (400MB) as a grey block.
Of course, resizing larger than the current volume size plus unallocated volume
space (I tried 1200MB) fails (diskdrake shows a "vextend failed" error.
(I actually encountered this on 9.1 with much larger volumes too).
It's not too serious, but it would be nice if everything worked exactly
correctly (everything else is really nice to use - diskdrake's LVM/XFS
resize/ext2,3 resize support etc makes it trivial to manage data).
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
