[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq1ehz3f26h.fsf@sermon.lab.mkp.net>
Date: Mon, 26 Sep 2011 17:01:42 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Joshua Scoggins <theoretically.x64@...il.com>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, Arun <engineerarun@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: Detection of Advanced Format drives
>>>>> "Joshua" == Joshua Scoggins <theoretically.x64@...il.com> writes:
Joshua> Keep in mind that some AF drives will not report their actual
Joshua> sector sizes. I have this issue with the WD AV-25 series. This
Joshua> is to provide compatibility with older operating systems that
Joshua> don't support AF drives. These are called generation 1
Joshua> devices. Newer drives will directly report their sector size as
Joshua> 4096 through the drive identify data older ones will say 512.
AF drives continue to report a logical block size of 512. There's an
additional parameter in IDENTIFY DEVICE that describes the physical
block size. Legacy operating systems do not check the physical block
size parameter. Linux does, and will bubble this additional information
up the stack.
There have been a few attempts at switching ATA drives over to 4KB
logical blocks as well. We are ready. However, both boot and legacy OS
compatibility concerns make this a bit of an uphill battle.
As you mention there's one vendor that pretty consistently gets their
physical block size reporting wrong. We've pointed this out to them many
times. Apparently it's been fixed with the latest green drive
firmware...
--
Martin K. Petersen Oracle Linux Engineering
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists