Bug 1804462

Summary: lshw reports wrong size for 4K native disk
Product: [Fedora] Fedora Reporter: Heinz Mauelshagen <heinzm>
Component: lshwAssignee: Terje Røsten <terje.rosten>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: terje.rosten, tuju
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-30 16:14:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Heinz Mauelshagen 2020-02-18 21:42:55 UTC

Comment 1 Heinz Mauelshagen 2020-02-18 21:45:02 UTC
# lshw -short|grep ST1
/0/100/2/0/8/0/0.0.0       /dev/sdv        volume         4588GiB ST1000NX0323

# smartctl -i /dev/sdv
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.18-200.fc31.x86_64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SEAGATE
Product:              ST1000NX0323
Revision:             K002
Compliance:           SPC-4
User Capacity:        1,000,204,886,016 bytes [1.00 TB]
Logical block size:   4096 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          2.5 inches
Logical Unit id:      0x5000c5007dcdbddb
Serial number:        S4700NVT0000J502HQCQ
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Tue Feb 18 22:44:39 2020 CET
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

Comment 2 Heinz Mauelshagen 2020-02-19 15:33:31 UTC
Tested lshw size report on a SATA attached 4K native disk ok
(sdu is SAS, sdbc is SATA, both 1TB as mentioned in the product spec).

# lshw -short | grep ST1
/0/100/2/0/8/0/0.0.0       /dev/sdu        volume         4588GiB ST1000NX0323
/0/100/2/0/10/0/1.c.0      /dev/sdbc       volume         931GiB ST1000NX0303

# [root@o ~]# cat /sys/block/{sdu,sdbc}/queue/{logical,physical}_block_size
4096
4096
4096
4096

Comment 3 Ben Cotton 2020-08-11 13:08:48 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 4 Ben Cotton 2021-11-04 17:41:00 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 5 Ben Cotton 2021-11-30 16:14:15 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.