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.
Bug 974871 - fsadm will not perform online resize when -v is set
Summary: fsadm will not perform online resize when -v is set
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-16 20:55 UTC by Wilbur Smith
Modified: 2013-10-10 12:57 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-10 12:57:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Wilbur Smith 2013-06-16 20:55:02 UTC
Description of problem:

When using fsadm -verbose to resize a newly extented LVM2 partition, an error message is displayed saying mounted / partitions can not be expamned while online. If -v is removed, online resize works correctly

Version-Release number of selected component (if applicable):

Kernel 2.6.32-358.111.1.openstack.el6.x86_64
LVM TOOLS 2.02.98(2)-RHEL6 (2012-10-15)

How reproducible:


Steps to Reproduce:
1. Use lvextend to add more space to an exsisting lvm2 partition
2. Attempt to run fsadm /dev/sda1/home -v  to extend partition
3. Error prints saying / mounted partitions can be extended while mounted

Actual results:

Volume would expand while online, but with virbose information on process

Expected results:

error is shown until -v is removed

Additional info:

Comment 2 Alasdair Kergon 2013-06-17 01:25:44 UTC
For reference, please would you paste into the bugzilla a transcript showing the two cases, the one that works and the identical one apart from -v that fails?

Comment 3 Alasdair Kergon 2013-06-17 01:30:08 UTC
- What filesystem type?

- Have you tried lvextend --resizefs?

- What happens if you use '--verbose' instead of the '-verbose' you say you used?

Comment 4 Wilbur Smith 2013-06-20 22:16:06 UTC
This is on an ext4 filesystem using LVM2. When I originally observed this, I tried both:
 fsadm resize /dev/vg_redshirt/lv_root 
               and 
fsadm resize /dev/vg_redshirt/lv_root 2048

Only by using the absolute number of blocks to expand was I able to get things to work.

I tried to recreate today can capture the output, but it is now working correctly for both use cases. When I originally tried to run this, my /root had 0 bytes of free space. After freeing up space, this command seems to work as expected.

Since this seems to be tied to a diskspace issue vs fsadm, I recomend we close this bug.

Comment 5 Zdenek Kabelac 2013-06-21 08:32:29 UTC
There could a problem with reporting errors when filesystem is full - since then code path depend on your settings of temporary directory.


Note You need to log in before you can comment on or make changes to this bug.