Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This can be trivially reproduced:
# touch pvfile
# truncate --size 12g pvfile
# losetup /dev/loop0 pvfile
# pvcreate /dev/loop0
# vgcreate testvg /dev/loop0
# lvcreate -L 4g testvg
# mkfs.ext4 /dev/mapper/testvg-lvol0
# mkdir -p /mnt/test
# mount /dev/mapper/testvg-lvol0 /mnt/test
then:
# lvextend -L +10G -r /dev/mapper/testvg-lvol0
fsck from util-linux-ng 2.17.2
e2fsck 1.41.10 (10-Feb-2009)
/dev/mapper/testvg-lvol0 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)?
At this point the administrator is one character away from clobbering their filesystem.
The lvm tools should not be attempting to run fsck on a mounted device.
I think that we should also look at removing the check for fsck before resizing. Seems to be similar to the run fsck every X boots theory, but hard coded here.
This code has been developed in 'dark' history of online resizing of ext2 & ext3 filesystem where some strange combination of needed checks were necessary.
lvextend obviously does support online resize without fs check involved - with usage of the option '-n' - but the code to force fsck has been left in.
I'll go through possible code paths and try to eliminate unwanted fsck calls and rather bailout whole command instead as some users may probably ignore those warning messages.
What would help a lot is that when fs is unmounted - check shouldn't be necessary.
(In reply to comment #8)
> What would help a lot is that when fs is unmounted - check shouldn't be
> necessary.
agreed, and for most filesystems it is not.
I'd just remove anything check-related at least for those filesystems that don't require it (xfs, I don't know about reiserfs...)
I can see about removing it for extN but upstream is paranoid.
The most pressing issue to fix here ASAP though, is not to bring the admin within an inch of corruption by starting a fsck on a -mounted- filesystem, that is hopefully something that can be fixed and pushed out right away.
-Eric
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0772.html