From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: L A Walsh <lkml@tlinx.org>
Cc: Karel Zak <kzak@redhat.com>,
"Dr. David Alan Gilbert" <dave@treblig.org>,
util-linux@vger.kernel.org
Subject: Re: does util-linux have a 'report sector size' util?
Date: Tue, 12 Mar 2019 18:11:41 +0000 [thread overview]
Message-ID: <20190312181141.l3hj2gf5l4dxiniy@gallifrey> (raw)
In-Reply-To: <5C87CA04.1010308@tlinx.org>
* L A Walsh (lkml@tlinx.org) wrote:
> On 3/12/2019 1:21 AM, Karel Zak wrote:
> > On Mon, Mar 11, 2019 at 02:34:46PM -0700, L A Walsh wrote:
> >
> >> On 3/11/2019 2:21 PM, Dr. David Alan Gilbert wrote:
> >>
> >>> * L A Walsh (lkml@tlinx.org) wrote:
> >>>
> >>>> Trying to track down why my 4K drives no longer display 4K
> >>>> in sysfs (/sys) and don't seem to show individual disk
> >>>> drive information. When I first got the drives, linux displayed
> >>>> the correct physical disk size, but when I look now, I only
> >>>> see 512.
> >>>>
> >>> Is this one of the PHY-SEC or LOG-SEC fields that lsblk can print?
> >>>
> >>> [dg@major ~]$ lsblk -o "NAME,PHY-SEC,LOG-SEC"
> >>> NAME PHY-SEC LOG-SEC
> >>> sda 512 512
> >>>
> >> ---
> >> It would be, if it was correct. Megacli displays:
> >>
> >> Sector Size: 512
> >> Logical Sector Size: 512
> >> Physical Sector Size: 4096
> >>
> >> But lsblk displays 512 for everything. The disk says it uses a 512e format
> >> with the 'e' meaning it emulates 512 even if not 512.
> >>
> >
> > lsblk, fdisk, blockdev, ... but all of the utils read the information
> > from kernel. So, it depends how the device reports topology to the
> > kernel.
> >
> Well, that's what I would think but I can't see why the device driver
> would have been purposely changed to hide the actual physical size or
> the temperature. That said, megacli has to be reading those values
> from somewhere -- and I'd tend to think it was accessing the driver as
> well, but that begs the question -- where is it getting the temperature
> and physical size from>?
>
> It can even read the serial numbers off the disks.
I think that's an easy one :-)
> I'm not sure if it is opensource or not.
> *sigh*
megacli is a special for LSI RAID controllers isn't it?
If so, then perhaps the RAID controller is hiding some info depending
on how it's configured and using a special to get the info from the controller.
How about trying one of the SCSI utils, like sginfo -a ?
Dave
>
> > Karel
> >
> >
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2019-03-12 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 20:57 does util-linux have a 'report sector size' util? L A Walsh
2019-03-11 21:21 ` Dr. David Alan Gilbert
2019-03-11 21:34 ` L A Walsh
2019-03-12 8:21 ` Karel Zak
2019-03-12 15:02 ` L A Walsh
2019-03-12 18:11 ` Dr. David Alan Gilbert [this message]
2019-03-15 14:05 ` Re:why would 4k size for phys sector size read in kernel, go away? L A Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190312181141.l3hj2gf5l4dxiniy@gallifrey \
--to=dave@treblig.org \
--cc=kzak@redhat.com \
--cc=lkml@tlinx.org \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).