From: Karel Zak <kzak@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Advanced Format disks mixed with regular disks?
Date: Tue, 22 Mar 2011 11:23:22 +0100 [thread overview]
Message-ID: <20110322102322.GK21093@nb.net.home> (raw)
In-Reply-To: <4D829D86.3050001@cox.net>
On Thu, Mar 17, 2011 at 06:47:18PM -0500, Ron Johnson wrote:
> On 03/16/2011 07:39 PM, Martin K. Petersen wrote:
>>>>>>> "Phillip" == Phillip Susi<psusi@cfl.rr.com> writes:
>>
>> Phillip> The kernel has the ability to read it from the drive and report
>> Phillip> it to the user space tools, which have been patched to use it,
>> Phillip> but the WD EARS drives lie and claim 512/512 instead of
>> Phillip> 512/4096.
>>
>> The saving grace is that modern util-linux/dm tooling aligns on 1MB by
>> default instead of sector 63.
>>
>
> So, given the correct options ( -c -b 4096 ), v2.17.2 will handle the 2TB
> WD Caviar Green WD20EARS drives which I just bought for my external
> backup device... Right?
The -b option is usually unnecessary (for v2.17 is the -c enough).
It seems (according to feedback from users) that newer WDxxEARS disks
are already fixed.
http://community.wdc.com/t5/Desktop/Problem-with-WD-Advanced-Format-drive-in-LINUX-WD15EARS/m-p/20675#M1245
Try
hdparm -I /dev/<disk>
to see more details, for example:
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
and
# cat /sys/block/<disk>/queue/physical_block_size
4096
It's also better to update to util-linux v2.18 or v2.19 where all the
new features are enabled by default (so -c is unnecessary too).
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-03-22 10:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 16:47 [linux-lvm] Advanced Format disks mixed with regular disks? Ron Johnson
2011-03-14 17:17 ` Mike Snitzer
2011-03-14 17:32 ` Les Mikesell
2011-03-14 18:02 ` Mike Snitzer
2011-03-14 18:09 ` Ron Johnson
2011-03-14 19:13 ` Ron Johnson
2011-03-14 20:00 ` Mike Snitzer
2011-03-15 8:02 ` Karel Zak
2011-03-15 14:24 ` Stuart D. Gathman
2011-03-15 17:36 ` Stuart D. Gathman
2011-03-15 0:15 ` John Drescher
2011-03-16 20:45 ` Phillip Susi
2011-03-16 22:55 ` Mike Snitzer
2011-03-16 23:11 ` Les Mikesell
2011-03-17 0:02 ` Mike Snitzer
2011-03-17 0:18 ` Mike Snitzer
2011-03-17 0:12 ` Phillip Susi
2011-03-17 0:39 ` Martin K. Petersen
2011-03-17 14:21 ` hansbkk
2011-03-17 23:47 ` Ron Johnson
2011-03-22 10:23 ` Karel Zak [this message]
2011-03-22 16:51 ` Les Mikesell
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=20110322102322.GK21093@nb.net.home \
--to=kzak@redhat.com \
--cc=linux-lvm@redhat.com \
/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).