Description of problem: $ lsblk | tail -2 sdb 8:16 0 900.0G 0 disk /home sdc 8:32 0 900.0G 0 disk sdb and sdc form a raid-1 btrfs volume, so the mountpoint should be shown for sdc too. Version-Release number of selected component (if applicable): util-linux-2.23.2-5.fc19.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
(In reply to Need Real Name from comment #0) > sdb and sdc form a raid-1 btrfs volume, so the mountpoint should be shown > for sdc too. Well, kernel VFS (/proc/self/mountinfo) contains info about only one device. All the relation device -> filesystem is inaccurate as filesystem does not have to be strictly related to a device. And the relation between btrfs raid members is also hidden for lsblk. I have doubts it's possible to fix it in an elegant way. We'll see.
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.
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.
Added to the upstream TODO file.
Just if anyone gets in here from a search engine, this issue is fixed in util-linux 2.38 root@node1:~/1# LD_LIBRARY_PATH=/root/1/.libs ./lsblk --version lsblk from util-linux 2.38 root@node1:~/1# LD_LIBRARY_PATH=/root/1/.libs ./lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sda nvme0n1 ├─nvme0n1p1 linux_raid_member rescue:0 08c6317a-6275-e859-b92b-22f9142ba7b0 │ └─md0 ext4 boot 355e8731-e4fe-43c2-aea9-356658938a58 761.6M 16% /boot └─nvme0n1p2 btrfs 1c13f595-e357-4b68-9ca7-4a17eb808bab 285.3G 40% / nvme2n1 ├─nvme2n1p1 linux_raid_member rescue:0 08c6317a-6275-e859-b92b-22f9142ba7b0 │ └─md0 ext4 boot 355e8731-e4fe-43c2-aea9-356658938a58 761.6M 16% /boot └─nvme2n1p2 btrfs 1c13f595-e357-4b68-9ca7-4a17eb808bab nvme1n1 root@node1:~/1# https://github.com/util-linux/util-linux/commit/2b1322f478d0149d3d570025dbec7cdf897b99a1
Oh, wait, it actually isn't. Got tricked by the double "/boot" output. Now that it's gone from TODO https://github.com/util-linux/util-linux/commit/2b1322f478d0149d3d570025dbec7cdf897b99a1 -- should it probably get back in there?
Yeah, this is (still) a problem for RAID 0 too. What shows with your /boot is a demo of the verifiable fact that md raid is able to get this right. Therefore, it is technically possible for btrfs to get it right too. I can't speak to whether Karel would say that whatever is done there is "elegant", of course. It might be super-gross!