From: Matthias Schniedermeyer <ms@citd.de>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: What are the correct mkfs.xfs parameters for a lying WD-EARS HDD?
Date: Tue, 9 Mar 2010 00:47:55 +0100 [thread overview]
Message-ID: <20100308234755.GA20269@citd.de> (raw)
In-Reply-To: <4B957E03.9090000@sandeen.net>
On 08.03.2010 16:45, Eric Sandeen wrote:
> Matthias Schniedermeyer wrote:
> > Hi
> >
> >
> > More than a month ago i bought 4 Western Digital WD15EARS (1.5 TB) which
> > are (AFAIK) the first general/commercial available 4k sector SATA-HDDs.
> >
> > Unfortunatly the HDDs lie about the 4k physical sector size and the most
> > prominent drawback is a worse than abysmal delete performance.
> > ("Normal" Read & Write-performance is OK)
> >
> > So if i wanted to (re-)mkfs the filesystems what would the correct
> > parameters be?
> >
> > Kernel/Userspace is pretty recent (Debian-SID):
> > mkfs.xfs version 3.1.1, kernel v2.6.33, util-linux 2.16.0
> > Not that that should matter when the HDDs lies.
>
> Recent kernel+util-linux-ng++fdisk+parted+xfsprogs -should- do the right thing for you....
> Oh, but this was maybe the drive that didn't output the right stuff when queried.
hdparm -I /dev/sdg | grep "Sector size"
Logical/Physical Sector size: 512 bytes
hdparm -V
hdparm v9.27
I vagely remember a posting on LKML that said it's a "known problem"
that the WD??EARS lie about physical sector size.
> Make sure your partitions, if any, are on 4k boundaries.(*) older fdisk at least
> won't do this by default, not sure about parted.
It's an encrypted loop at am 4k offset to leave space for a fake MBR
(and more importantly a signature for a custom udev-script).
> once that is done, tell mkfs.xfs "-s size=4096" to set the 4k sector size
So that should be enough?
Time for backup/mkfs/restore then.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-03-08 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 22:10 What are the correct mkfs.xfs parameters for a lying WD-EARS HDD? Matthias Schniedermeyer
2010-03-08 22:45 ` Eric Sandeen
2010-03-08 23:47 ` Matthias Schniedermeyer [this message]
2010-03-09 21:41 ` Matthias Schniedermeyer
2010-03-10 8:26 ` Gim Leong Chin
2010-03-08 23:55 ` Martin K. Petersen
2010-03-09 0:55 ` Eric Sandeen
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=20100308234755.GA20269@citd.de \
--to=ms@citd.de \
--cc=sandeen@sandeen.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.