From: "Gerd v. Egidy" <lists@egidy.de>
To: linux-kernel@vger.kernel.org
Subject: how to read block device size from sysfs?
Date: Wed, 1 Dec 2010 17:29:18 +0100 [thread overview]
Message-ID: <201012011729.18661.lists@egidy.de> (raw)
Hi,
I want to read the size of a block device in bytes from sysfs.
There are /sys/block/<device>/size and
/sys/block/<device>/<device><partition>/size.
But these values are reported in sectors, not in bytes. As discs with 4K
sectors are on the horizon now, I don't want to make wrong assumptions on the
sector size.
So what is the correct sector size for /sys/block/<device>/size?
/sys/block/<device>/queue/logical_block_size,
/sys/block/<device>/queue/physical_block_size or something else?
While searching for an answer I've stumbled across some reports about drives
lying about their sector sizes to "improve" compatibility. Is there some best
practice to still get the correct size in bytes?
Kind regards,
Gerd
--
Address (better: trap) for people I really don't want to get mail from:
jonas@cactusamerica.com
reply other threads:[~2010-12-01 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201012011729.18661.lists@egidy.de \
--to=lists@egidy.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.