Bug 1358748
| Summary: | lshw does not report devices which have pv's created on them (on the entire device) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | nikhil kshirsagar <nkshirsa> |
| Component: | lshw | Assignee: | Petr Oros <poros> |
| Status: | CLOSED ERRATA | QA Contact: | Mike Gahagan <mgahagan> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.1 | CC: | poros, skozina |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | lshw-B.02.17-12.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-04 03:47:08 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: | |||
After deep inspection i found reason why lshw drop device from list.
[root@localhost]# lshw -c disk
*-virtio2
description: Virtual I/O device
physical id: 0
bus info: virtio@2
logical name: /dev/vdb
size: 20GiB (21GB)
configuration: driver=virtio_blk logicalsectorsize=512 sectorsize=512
[root@localhost]#
[root@localhost]# pvcreate /dev/vdb
Physical volume "/dev/vdb" successfully created
[root@localhost]# lshw -c disk
[root@localhost]#
but:
[root@localhost]# lshw -c volume
*-virtio2
description: Virtual I/O device
physical id: 0
bus info: virtio@2
logical name: /dev/vdb
serial: 9Q74c8-Kc2D-0EHu-gBPe-Gowc-wytU-cIiczq
size: 20GiB
capacity: 20GiB
capabilities: lvm2
configuration: driver=virtio_blk logicalsectorsize=512 sectorsize=512
This is caused by these lines in partitions.cc
In function scan_partitions:
if(!medium->isCapable("partitioned"))
{
if(scan_volume(*medium, s)) // whole disk volume?
medium->setClass(hw::volume);
}
That means, when volume is whole disk, lshw classify device like volume, not like disk.
Confirmed an empty PV encompassing an entire disk (in this case a USB key) will show up as a disk, not as a volume... the pv itself will show as a medium under the disk entry. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-2326.html |
Description of problem: when whole disk is considered as PV, the disk is not found in the lshw output. Version-Release number of selected component (if applicable): lshw-B.02.17-5.el7.x86_64 How reproducible: create a pv on /dev/sdb (or any disk) lshw will not list it. Steps to Reproduce: see below in additional info Actual results: disks not found in lshw output even though they exist. The disks not found have pvs on them (entire device, no partitions) Expected results: lshw should report pv's Additional info: [root@dhcp6-217 src]# fdisk -l Disk /dev/vda: 10.7 GB, 10737418240 bytes, 20971520 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000df364 Device Boot Start End Blocks Id System /dev/vda1 * 2048 1026047 512000 83 Linux /dev/vda2 1026048 20971519 9972736 8e Linux LVM Disk /dev/sda: 3221 MB, 3221225472 bytes, 6291456 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/rhel_dhcp6--217-root: 9093 MB, 9093251072 bytes, 17760256 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/rhel_dhcp6--217-swap: 1073 MB, 1073741824 bytes, 2097152 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb: 2147 MB, 2147483648 bytes, 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes [root@dhcp6-217 src]# pvs PV VG Fmt Attr PSize PFree /dev/sda lvm2 --- 3.00g 3.00g /dev/sdb lvm2 --- 2.00g 2.00g /dev/vda2 rhel_dhcp6-217 lvm2 a-- 9.51g 40.00m [root@dhcp6-217 src]# lshw -class disk *-cdrom description: SCSI CD-ROM physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/cdrom logical name: /dev/sr0 capabilities: audio configuration: status=nodisc [root@dhcp6-217 src]# ---------------------------------------------------------------------------------------------- <nkshirsa> i looked at the lshw code to understand why pv's are not being reported, it seems like they are being reported in the scan_scsi and scan_device methods, (i can see the device on which i have made pv), but when it arrives to print (which is a complex recursive call and i cannot seem to be able to print node through gdb) it doesnt have that device to be printed) <nkshirsa> i think the issue is while printing.. <poros> really? where? <nkshirsa> during building the computer node, i can see its finding the disks and even marking them as lvm disks.. <nkshirsa> but when it calls print from the main function in lshw.cc , its not able to find the recursive structures inside while printing .. so it never prints them.. <nkshirsa> i ran it through gdb and i can see scan_partitions and scan_lvm being called and correctly populated for the pv's <nkshirsa> but once it prints, it goes into several levels of recursion and im having trouble printing the vector node, config, resources through gdb, so i lose track of where i am in the tree.. but i am sure its not finding those disk objects and therefore not printing them <nkshirsa> anyway, im done for today, please let me know if you do understand why the pv's are not being printed. i am now filing bz and will put all the investigation so far in it, it will get assigned to you i guess. <poros> ok