Bug 980463

Summary: lsblk is not showing mounted renamed LV device
Product: [Fedora] Fedora Reporter: Zdenek Kabelac <zkabelac>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: agk, jonathan, kzak, mluscon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 01:39:18 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 Zdenek Kabelac 2013-07-02 12:55:12 UTC
Description of problem:

When the filesystem on LV is mounted,
and i.e. volume group name is changed,
lsblk will not display mount point of mounted renamed device
(since in the /proc/mounts || /proc/self/mountinfo device 
stays with the old - now no longer existing name)

Unsure about lsblk internal implementation,
but I assume lsblk should match major/minor instead of names.

Version-Release number of selected component (if applicable):
util-linux-2.23.1-3.fc20.x86_64

How reproducible:


Steps to Reproduce:
1. create LV & mkfs & mount
2. lvrename
3. lsblk  

Actual results:

Mounted device doesn't have mountpoint present

Expected results:

Renamed mounted device has proper mountpoint

Additional info:

Comment 1 Karel Zak 2013-07-08 12:28:01 UTC
Thanks. Fixed by upstream commit da531dd8d5d3aa284b7f73ce6345e54ce3b3bc1d. Fedora package will be updated ASAP.

Note that we cannot completely rely on devno, because maj:min in /proc/self/mountinfo does not have to match with device numbers for same filesystems (e.g. btrfs).

Comment 2 Fedora Update System 2013-07-31 13:30:10 UTC
util-linux-2.23.2-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/util-linux-2.23.2-1.fc19

Comment 3 Fedora Update System 2013-08-02 03:33:08 UTC
Package util-linux-2.23.2-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing util-linux-2.23.2-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-13967/util-linux-2.23.2-1.fc19
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-09-10 09:52:21 UTC
util-linux-2.23.2-4.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/util-linux-2.23.2-4.fc19

Comment 5 Fedora End Of Life 2013-09-16 17:08:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 6 Zdenek Kabelac 2015-03-12 10:02:25 UTC
Works for me. However tested with:
util-linux-2.26-2.fc23.x86_64

Comment 7 Fedora End Of Life 2015-05-29 09:09:09 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2015-06-30 01:39:18 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.