From: Khelben Blackstaff <eye.of.the.8eholder@gmail.com>
To: xfs@oss.sgi.com
Subject: Re: 4k sector drives
Date: Wed, 21 Jul 2010 13:33:48 +0300 [thread overview]
Message-ID: <201007211333.48363.eye.of.the.8eholder@gmail.com> (raw)
> I have these:
> Model=WDC WD20EARS-00MVWB0, FwRev=50.0AB50, SerialNo=WD-WMAZ20035646
> Model=WDC WD20EARS-00MVWB0, FwRev=50.0AB50, SerialNo=WD-WMAZ20028252
> Any chance to get Linux know they are 4k sector drives manually?
Your revision numbers are different than mine, because you have the 2TB drive,
but i guess its the same for these too. You can try "hdparm -I /dev/sdX" (capital i)
or "cat /sys/block/sdX/queue/hw_sector_size" to see what they report.
Mine report "Logical/Physical Sector size: 512 bytes"
There are newer revisions that report "Physical Sector size: 4096 bytes"
Nevertheless, you don't have to get them to report 4k to linux. As long as you
align the partitions its fine. As i said in the other post, newer fdisk doesn't use
"DOS compatibility mode" and uses sectors by default (instead of stupid CHS)
with a 1MB alignment, so every partition will be properly aligned. If you don't
dual boot Windows, you can also use GPT partitioning scheme.
Also, from what i have seen, xfsprogs are quite clever and find most stuff on
their own. I usually mkfs with "-s size=4096" just to be sure.
Slightly offtopic, there is another "problem" with these drives. They park the heads
every 8 seconds, so they _might_ wear prematurely. You can change the 8sec timer
or disable it with the wdidle3 utility from this url
http://support.wdc.com/product/download.asp?groupid=609&sid=113&lang=en
If you want to know more about the problem, there are many forums where
you can read about wdidle3 and i also posted about it on my blog.
http://lordkhelben.wordpress.com/2010/05/15/wd-caviar-green-hard-disks-idle-settings/
I hope i helped.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-07-21 10:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 10:33 Khelben Blackstaff [this message]
2010-07-21 12:21 ` 4k sector drives Michael Monnerie
2010-07-23 6:09 ` Michael Monnerie
2010-07-23 9:58 ` Christoph Hellwig
2010-07-23 10:42 ` Stan Hoeppner
2010-07-23 10:47 ` Christoph Hellwig
2010-07-23 12:41 ` Stan Hoeppner
2010-07-23 10:59 ` Michael Monnerie
2010-07-23 12:56 ` Emmanuel Florac
2010-07-23 13:10 ` Stan Hoeppner
2010-07-23 13:38 ` Matthias Schniedermeyer
2010-07-23 13:50 ` Emmanuel Florac
2010-07-23 14:13 ` Matthias Schniedermeyer
2010-07-24 8:47 ` Christoph Hellwig
2010-07-24 21:07 ` Eric Sandeen
2010-07-24 22:35 ` Michael Monnerie
2010-07-25 15:33 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2010-07-23 15:02 Khelben Blackstaff
2010-07-23 15:28 ` Emmanuel Florac
2010-07-23 9:19 Khelben Blackstaff
2010-07-21 7:53 Khelben Blackstaff
2010-07-21 9:14 ` Michael Monnerie
2010-07-21 10:33 ` Emmanuel Florac
2010-07-20 18:58 Michael Monnerie
2010-07-20 20:30 ` Stan Hoeppner
2010-07-20 20:39 ` Emmanuel Florac
2010-07-20 21:34 ` Michael Monnerie
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=201007211333.48363.eye.of.the.8eholder@gmail.com \
--to=eye.of.the.8eholder@gmail.com \
--cc=xfs@oss.sgi.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