Bug 1596162
| Summary: | Command 'lsblk -I <MAJ>' does not perform according to manual. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ricky.tigg | ||||
| Component: | util-linux | Assignee: | Karel Zak <kzak> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 28 | CC: | jonathan, kzak, ricky.tigg | ||||
| Target Milestone: | --- | ||||||
| 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: | 2018-08-24 10:04:49 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: | |||||||
| Attachments: |
|
||||||
|
Description
ricky.tigg
2018-06-28 10:59:25 UTC
well, I think -I, --include <list> show only devices with specified major numbers is good enough for --help and I guess man page contains all necessary information, but we can improve it -- any suggestion? The top-level device is a device without dependence, I think it's pretty obvious from lsblk tree-like output. The problem I see is --list output. In this case the filter is applied in the same way as for tree-like output, but dependence between devices is not obvious from the output. Maybe we can add a note about it in the man page. The current behaviour is correct $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk ├─sda1 8:1 0 200M 0 part /boot/efi ├─sda2 8:2 0 200M 0 part /boot ├─sda3 8:3 0 130.3G 0 part ├─sda4 8:4 0 50G 0 part / ├─sda5 8:5 0 35.1G 0 part └─sda6 8:6 0 7.8G 0 part sdb 8:16 0 74.5G 0 disk └─sdb1 8:17 0 74.5G 0 part /home/archive sdc 8:32 0 100M 0 disk └─vg_test-lv_test 253:0 0 12M 0 lvm nvme0n1 259:0 0 223.6G 0 disk ├─nvme0n1p1 259:1 0 7.8G 0 part ├─nvme0n1p2 259:2 0 200G 0 part /home └─nvme0n1p3 259:3 0 15.8G 0 part /home/test # lsblk -I 8 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk ├─sda1 8:1 0 200M 0 part /boot/efi ├─sda2 8:2 0 200M 0 part /boot ├─sda3 8:3 0 130.3G 0 part ├─sda4 8:4 0 50G 0 part / ├─sda5 8:5 0 35.1G 0 part └─sda6 8:6 0 7.8G 0 part sdb 8:16 0 74.5G 0 disk └─sdb1 8:17 0 74.5G 0 part /home/archive sdc 8:32 0 100M 0 disk └─vg_test-lv_test 253:0 0 12M 0 lvm Created attachment 1459797 [details]
Opensuse graphical partition tool
At least for my use that tool suits me rather well; it appears to be the only one –even if it is as text-based interface– available for that distribution that provides a comparable feature to the graphical one proper to the distribution Opensuse. Though the addition of a feature covering volumes' free space would be welcome.
Yes, I have already thought about free/used space columns -- the problem is that such info is mostly about filesystems and in cases where FS:DEV is not 1:1 (RAIDs, btrfs, etc) the result may be confusing for end users. We'll see... |