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.

Bug 1320735

Summary: renaming logical volumes to previously existing volume names causes confusion when lvresize calls fsadm to extend
Product: Red Hat Enterprise Linux 6 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: Changing Logical Volumes (RHEL6) QA Contact: cluster-qe <cluster-qe>
Status: CLOSED NEXTRELEASE Docs Contact:
Severity: medium    
Priority: unspecified CC: agk, heinzm, jbrassow, msnitzer, prajnoha, prockai, zkabelac
Version: 6.8   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-02 09:42:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Corey Marthaler 2016-03-23 21:25:35 UTC 
Description of problem:
This is the extend issue described in comment #12 and #14 of bug 1196910.

host-118.virt.lab.msp.redhat.com: lvcreate  --nosync --type raid1 -m 1 -n resizeA -L 200M raid_sanity
  WARNING: New raid1 won't be synchronised. Don't read what you didn't write!
Placing an ext on resizeA volume
mkfs /dev/raid_sanity/resizeA
mke2fs 1.41.12 (17-May-2010)
mount /dev/raid_sanity/resizeA /mnt/resizeA

host-118.virt.lab.msp.redhat.com: lvcreate  --nosync --type raid1 -m 1 -n resizeB -L 200M raid_sanity
  WARNING: New raid1 won't be synchronised. Don't read what you didn't write!
Placing an ext on resizeB volume
mkfs /dev/raid_sanity/resizeB
mke2fs 1.41.12 (17-May-2010)
mount /dev/raid_sanity/resizeB /mnt/resizeB

lvrename /dev/raid_sanity/resizeA /dev/raid_sanity/resizeC
lvrename /dev/raid_sanity/resizeB /dev/raid_sanity/resizeA

[root@host-118 ~]# lvs -a -o +devices
  LV                 VG          Attr       LSize    Cpy%Sync Devices
  resizeA            raid_sanity Rwi-aor--- 200.00m  100.00   resizeA_rimage_0(0),resizeA_rimage_1(0)
  [resizeA_rimage_0] raid_sanity iwi-aor--- 200.00m           /dev/sde2(52)
  [resizeA_rimage_1] raid_sanity iwi-aor--- 200.00m           /dev/sde1(52)
  [resizeA_rmeta_0]  raid_sanity ewi-aor---   4.00m           /dev/sde2(51)
  [resizeA_rmeta_1]  raid_sanity ewi-aor---   4.00m           /dev/sde1(51)
  resizeC            raid_sanity Rwi-aor--- 200.00m  100.00   resizeC_rimage_0(0),resizeC_rimage_1(0)
  [resizeC_rimage_0] raid_sanity iwi-aor--- 200.00m           /dev/sde2(1)
  [resizeC_rimage_1] raid_sanity iwi-aor--- 200.00m           /dev/sde1(1)
  [resizeC_rmeta_0]  raid_sanity ewi-aor---   4.00m           /dev/sde2(0)
  [resizeC_rmeta_1]  raid_sanity ewi-aor---   4.00m           /dev/sde1(0)

[root@host-118 ~]# lvextend -r -n -f -L 400M /dev/raid_sanity/resizeA
  Extending 2 mirror images.
  Size of logical volume raid_sanity/resizeA changed from 200.00 MiB (50 extents) to 400.00 MiB (100 extents).
  Logical volume resizeA successfully resized.
resize2fs 1.41.12 (17-May-2010)
resize2fs: Device or resource busy while trying to open /dev/mapper/raid_sanity-resizeA
Couldn't find valid filesystem superblock.
fsadm: Resize ext2 failed
  fsadm failed: 1



Version-Release number of selected component (if applicable):
2.6.32-633.el6.x86_64

lvm2-2.02.143-3.el6    BUILT: Tue Mar 22 09:26:10 CDT 2016
lvm2-libs-2.02.143-3.el6    BUILT: Tue Mar 22 09:26:10 CDT 2016
lvm2-cluster-2.02.143-3.el6    BUILT: Tue Mar 22 09:26:10 CDT 2016
udev-147-2.72.el6    BUILT: Tue Mar  1 06:14:05 CST 2016
device-mapper-1.02.117-3.el6    BUILT: Tue Mar 22 09:26:10 CDT 2016
device-mapper-libs-1.02.117-3.el6    BUILT: Tue Mar 22 09:26:10 CDT 2016
device-mapper-event-1.02.117-3.el6    BUILT: Tue Mar 22 09:26:10 CDT 2016
device-mapper-event-libs-1.02.117-3.el6    BUILT: Tue Mar 22 09:26:10 CDT 2016
device-mapper-persistent-data-0.6.2-0.1.rc7.el6    BUILT: Tue Mar 22 08:58:09 CDT 2016
cmirror-2.02.143-3.el6    BUILT: Tue Mar 22 09:26:10 CDT 2016
Comment 2 Corey Marthaler 2017-05-26 15:07:50 UTC 
Looks like current behavior (in rhel7.4) is now:

lvm2-2.02.171-2.el7    BUILT: Wed May 24 09:02:34 CDT 2017

lvextend -r -n -f -L 1.5G /dev/snapper_thinp/other1
  WARNING: Sum of all thin volume sizes (6.50 GiB) exceeds the size of thin pool snapper_thinp/POOL (1.00 GiB)!
fsadm: Cannot RESIZE device "/dev/mapper/snapper_thinp-other1" without umounting filesystem /mnt/other2 first.
fsadm: Mounted filesystem is using device snapper_thinp-other1, but referenced device is snapper_thinp-other2.
fsadm: Filesystem utilities currently do not support renamed devices.
  /usr/sbin/fsadm failed: 1