Using the -r option to extend an LV, and even if the answer is NO, the extension continue and the online filesystem is extended.
As the question is on the first moment of the procedure, I expect that all activities should be aborted.
This is the result of the command
# lvextend -r -L+50G /dev/vg_1TB_01/lv_Foto_01
fsck from util-linux-ng 2.18
e2fsck 1.41.12 (17-May-2010)
/dev/mapper/vg_1TB_01-lv_Foto_01 è montato.
WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.
Continuare (s/n)? no
Extending logical volume lv_Foto_01 to 250,00 GiB
Logical volume lv_Foto_01 successfully resized
resize2fs 1.41.12 (17-May-2010)
Filesystem at /dev/dm-1 is mounted on /mnt/1TB_01/Foto; on-line resizing required
old desc_blocks = 13, new_desc_blocks = 16
Performing an on-line resize of /dev/dm-1 to 65536000 (4k) blocks.
The filesystem on /dev/dm-1 is now 65536000 blocks long.
I assume you are using the latest available lvm2 package for F14 - however it needs newer package of lvm2.
I believe this bug has been fixed in lvm2 2.02.75.
I think next rebased version will be based either on 2.02.84 or 2.02.85.
Actually I use the lvm2-2.02.73-3.fc14.i686.rpm.
yum update actually doesn't offer a new version for them.
lvm2-2.02.84-2.fc14 has been submitted as an update for Fedora 14.
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lvm2-2.02.84-2.fc14'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
lvm2-2.02.84-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.