From: "José Félix Ontañón" <felixonta@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: About volume/disk blocks/size properties
Date: Wed, 19 Jan 2011 22:34:53 +0000 [thread overview]
Message-ID: <AANLkTikg0L+Zv7JSpfAkeCtSDfEtheFjWLNsU069iaz8@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=zsM5nY+J9X7-Soe_5Ajn1Qek6TEhWgpWj-ra2@mail.gmail.com>
El día 19 de enero de 2011 14:38, Karel Zak <kzak@redhat.com> escribió:
> On Mon, Jan 10, 2011 at 12:07:41AM +0100, José Félix Ontañón wrote:
>> El día 8 de enero de 2011 18:26, Kay Sievers <kay.sievers@vrfy.org> escribió:
>> > 2011/1/8 José Félix Ontañón <felixonta@gmail.com>:
>> >> I wonder... are there any reasons for not being convenient to export
>> >> some properties refering the volume size of a disk device?
>> >> Although I'm concerned about the
>> >> don't-turning-udev-into-a-hal-like-system, I still perceiving the
>> >> volume.size or volume.block_size properties as very useful for user
>> >> space apps.
>> >>
>> >> On the one hand, it could be easy for user space apps to get the
>> >> size/blocks for partition devices,
>> >
>> > $ grep . /sys/class/block/*/size
>> > /sys/class/block/sda1/size:41943040
>> > /sys/class/block/sda2/size:41943040
>> > /sys/class/block/sda3/size:115343360
>> > /sys/class/block/sda4/size:50835456
>> > /sys/class/block/sda/size:250069680
>> > /sys/class/block/sr0/size:2097151
>> >
>> >> but on the other hand you need root
>> >> privs to get this info for disk devices, am i wrong?
>> >
>> > Everybody can do that.
>> >
>> > Kay
>> >
>>
>> Oh! Much better! Sorry for messing up.
>>
>> It seems the size file give us the number of sectors, isn't?
>> In order to get the bytes of the disk/partition ... is it right to
>> multiply /sys/block/<disk>/queue/logical_block_size times
>> /sys/block/<disk>/size ??
>
> The latest util-linux version (2.19-rc1) contains a new "lsblk" util,
> for example:
>
> $ lsblk -b
> NAME MAJ:MIN RM SIZE RO MOUNTPOINT
> sda 8:0 0 100030242816 0
> ├─sda1 8:1 0 106896384 0
> ├─sda2 8:2 0 1024 0
> ├─sda3 8:3 0 2410007040 0 [SWAP]
> ├─sda4 8:4 0 81783959040 0 /
> ├─sda5 8:5 0 10742183424 0
> │ └─kzak-home (dm-0) 253:0 0 10741655040 0 /home/kzak
> └─sda6 8:6 0 4984487424 0 /boot
>
> more at http://karelzak.blogspot.com/2010/12/lsblk8.html
>
> Karel
Thaks Karel, i'll check that improvement on util-linux for taking
ideas about how you access /proc information.
Cheers!
> --
> Karel Zak <kzak@redhat.com>
> http://karelzak.blogspot.com
>
--
http://fontanon.org
prev parent reply other threads:[~2011-01-19 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 12:53 About volume/disk blocks/size properties José Félix Ontañón
2011-01-08 17:26 ` Kay Sievers
2011-01-09 23:07 ` José Félix Ontañón
2011-01-10 0:44 ` Kay Sievers
2011-01-19 13:38 ` Karel Zak
2011-01-19 22:34 ` José Félix Ontañón [this message]
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=AANLkTikg0L+Zv7JSpfAkeCtSDfEtheFjWLNsU069iaz8@mail.gmail.com \
--to=felixonta@gmail.com \
--cc=linux-hotplug@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).