Re: Detection of Advanced Format drives

From: Arun
Date: Tue Sep 27 2011 - 17:12:34 EST


Mark,

I got your point.

A quick check of hdparm tells me that it is using the SG_IO ioctl for
the ATA_OP_PIDENTIFY command. Maybe I have some hopes of having a
correct result with the BLKPBSZGET ioctl. Will check that out.

Regards,

Arun



On Wed, Sep 28, 2011 at 01:40, Mark Knecht <markknecht@xxxxxxxxx> wrote:
>
> On Tue, Sep 27, 2011 at 11:59 AM, Martin K. Petersen
> <martin.petersen@xxxxxxxxxx> wrote:
> >>>>>> "Arun" == Arun  <engineerarun@xxxxxxxxx> writes:
> >
> > Arun> Should I suppose that it is an already available piece of
> > Arun> information to the userland?
> >
> > Yes, in the sysfs locations Mike mentioned:
> >
> >  /sys/block/foo/queue/physical_block_size
> >
> > Or you can use the BLKPBSZGET ioctl.
> >
> >
> > Arun> Or do I need to modify the hdparm/fdisk code to get this piece of
> > Arun> info?
> >
> > Recent hdparm versions will also report the right thing:
> >
> > # hdparm -I /dev/sdc | grep Sector
> >        Logical  Sector size:                   512 bytes
> >        Physical Sector size:                  4096 bytes
> >        Logical Sector-0 offset:                512 bytes
> >
> > --
> > Martin K. Petersen      Oracle Linux Engineering
>
> As someone else pointed out earlier, not every drive with 4K sectors
> will tell you it has 4K sectors, at least not using hdparm. This is a
> WD 1TB drive circa early last year for which I've not updated
> firmware. (If there is an update)
>
> gandalf ~ # hdparm -I /dev/sda | grep Sector
>        Logical/Physical Sector size:           512 bytes
> gandalf ~ #
>
> gandalf ~ # cat /sys/block/sda/queue/physical_block_size
> 512
> gandalf ~ #
>
> - Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/