From: Niels <zorglub_olsen@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Slow disks.
Date: Sun, 26 Dec 2010 23:07:45 +0100 [thread overview]
Message-ID: <if8ebj$nf8$1@dough.gmane.org> (raw)
In-Reply-To: 4D14BB36.1030304@msgid.tls.msk.ru
On Friday 24 December 2010 16:24, Michael Tokarev wrote:
[snip]
> The thing is, for these WD*EARS drivers, it is _vital_ to get
> proper alignment of all partitions and operations. They've
> 4Kb sectors physically but report 512bytes sectors to the OS.
> It is _essential_ to ensure all partitions are aligned to the
> 4Kb sectors. Be it LVM, raid-something, etc - each filesystem
> must start at a 4kb boundary at least, or else you'll see
> _dramatic_ write speed problems.
>
> So.. check the whole storage stack and ensure proper alignment
> everywhere. In particular, check that your partitions are not
> aligned to 63 sectors (512b), or starts at N+1 sector - the
> most problematic mode for these drives.
[snip]
I have several of these drives, in various sizes. They seem to be aligned to
63 as you mention:
Device Boot Start End Blocks Id System
/dev/sda1 63 208844 104391 83 Linux
/dev/sda2 208845 19759949 9775552+ 82 Linux swap / Solaris
/dev/sda3 19759950 215094284 97667167+ 83 Linux
/dev/sda4 215094285 781417664 283161690 83 Linux
Device Boot Start End Blocks Id System
/dev/sdb1 63 1953520064 976760001 83 Linux
Is that bad?
What can I do to repair it?
What can I do to prevent it from happening again?
Thanks,
Niels
next prev parent reply other threads:[~2010-12-26 22:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 14:15 Slow disks Rogier Wolff
2010-12-20 18:06 ` Bruno Prémont
2010-12-20 18:32 ` Greg Freemyer
2010-12-22 10:43 ` Rogier Wolff
2010-12-22 15:59 ` Greg Freemyer
2010-12-22 16:27 ` Jeff Moyer
2010-12-22 22:44 ` Rogier Wolff
2010-12-23 14:40 ` Jeff Moyer
2010-12-23 17:01 ` Rogier Wolff
2010-12-23 17:47 ` Jeff Moyer
2010-12-23 18:51 ` Greg Freemyer
2010-12-23 19:10 ` Jaap Crezee
2010-12-23 22:09 ` Greg Freemyer
2010-12-24 11:40 ` Rogier Wolff
2010-12-26 23:05 ` Greg Freemyer
2010-12-27 0:27 ` Rogier Wolff
2010-12-24 10:45 ` Rogier Wolff
2010-12-23 17:05 ` Jaap Crezee
2010-12-26 23:38 ` Mark Knecht
2010-12-27 0:34 ` Rogier Wolff
2010-12-27 3:12 ` Mark Knecht
2010-12-27 18:20 ` Krzysztof Halasa
2010-12-24 13:01 ` Krzysztof Halasa
2010-12-24 15:24 ` Michael Tokarev
2010-12-24 20:58 ` Krzysztof Halasa
2010-12-25 12:14 ` Rogier Wolff
2010-12-25 12:19 ` Mikael Abrahamsson
2010-12-25 18:12 ` Jaap Crezee
2010-12-25 21:28 ` Michael Tokarev
2010-12-26 21:40 ` Rogier Wolff
2010-12-26 23:17 ` Greg Freemyer
2010-12-26 23:49 ` Rogier Wolff
2010-12-26 22:07 ` Niels [this message]
2010-12-27 10:56 ` Tejun Heo
2010-12-20 19:09 ` Jeff Moyer
2010-12-22 20:52 ` David Rees
2010-12-22 22:46 ` Rogier Wolff
2010-12-22 23:13 ` David Rees
[not found] <fa.C+PyZdFdHUxRFDJDF3KlrfaJASk@ifi.uio.no>
2010-12-21 12:29 ` Arto Jantunen
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='if8ebj$nf8$1@dough.gmane.org' \
--to=zorglub_olsen@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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