On Wed, Jun 27, 2012 at 01:42:27AM +0300, Pasi Kärkkäinen wrote:
> On Fri, Jun 15, 2012 at 06:23:42PM -0500, Timothy Coalson wrote:
> > Sorry, if you meant distinguishing between true 512 and emulated
> > 512/4k, I don't know, it may be vendor-specific as to whether they
> > expose it through device commands at all.
> >
>
> At least on Linux you can see the info from:
>
> /sys/block/<disk>/queue/logical_block_size=512
> /sys/block/<disk>/queue/physical_block_size=4096
>
Oh, and also these methods work on Linux:
# hdparm -I /dev/sdc | grep Sector
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 512 bytes
And then there's the BLKPBSZGET ioctl.
So I'd be surprised if that stuff isn't implemented on *solaris..
-- Pasi
>
> > Tim
> >
> > On Fri, Jun 15, 2012 at 6:02 PM, Timothy Coalson <tsc...@mst.edu> wrote:
> > > On Fri, Jun 15, 2012 at 5:35 PM, Jim Klimov <jimkli...@cos.ru> wrote:
> > >> 2012-06-16 0:05, John Martin wrote:
> > >>>>
> > >>>> Its important to know...
> > >>>
> > >>> ...whether the drive is really 4096p or 512e/4096p.
> > >>
> > >>
> > >> BTW, is there a surefire way to learn that programmatically
> > >> from Solaris or its derivates
> > >
> > > prtvtoc <device> should show the block size the OS thinks it has. Or
> > > you can use format, select the disk from a list that includes the
> > > model number and size, and use "verify".
> > >
> > > Tim
> > _______________________________________________
> > zfs-discuss mailing list
> > zfs-discuss@opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
