From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id o28Nka4T083319 for ; Mon, 8 Mar 2010 17:46:36 -0600 Received: from enyo.dsw2k3.info (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id E2E731D14560 for ; Mon, 8 Mar 2010 15:48:07 -0800 (PST) Received: from enyo.dsw2k3.info (enyo.dsw2k3.info [195.71.86.239]) by cuda.sgi.com with ESMTP id zZYLMWs7bvg1FTcw for ; Mon, 08 Mar 2010 15:48:07 -0800 (PST) Date: Tue, 9 Mar 2010 00:47:55 +0100 From: Matthias Schniedermeyer Subject: Re: What are the correct mkfs.xfs parameters for a lying WD-EARS HDD? Message-ID: <20100308234755.GA20269@citd.de> References: <20100308221044.GA17830@citd.de> <4B957E03.9090000@sandeen.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4B957E03.9090000@sandeen.net> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Eric Sandeen Cc: xfs@oss.sgi.com 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