public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#661580: mkfs.xfs fails to detect correct sector size
Date: Tue, 28 Feb 2012 08:49:14 +0100	[thread overview]
Message-ID: <20120228074914.31280.78231.reportbug@frosties.localnet> (raw)

Package: xfsprogs
Version: 3.1.7
Severity: important
File: /sbin/mkfs.xfs

Hi,

since I recently bought a harddisk with 4K sector size I've been
checking for correct alignment and blocksizes in various things. One
of them being xfs.

When I partition the disk in parted it shows correctly to have a
logical blocksize of 512 byte and physical blocksize of 4096 byte.
But mkfs.xfs does not detect that the physical blocksize is 4096 byte
and creates a filesystem with:

meta-data=/dev/sde1              isize=256    agcount=32, agsize=22892696 blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=732566272, imaxpct=5
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal               bsize=4096   blocks=357698, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0


This often results in access to the disk that is not aligned to the
blocksize with the resulting degradation in performance.

Further, manually selecting the right sector size of 4096 still causes
lots of unaligned access while formating and while mounting the
filesystem. It does seem to fix the problem for actual use though.

MfG
	Goswin

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages xfsprogs depends on:
ii  libblkid1     2.20.1-1
ii  libc6         2.13-21 
ii  libreadline5  5.2-11  
ii  libuuid1      2.19.1-5

xfsprogs recommends no packages.

Versions of packages xfsprogs suggests:
pn  acl      2.2.51-4  
pn  attr     1:2.4.46-3
pn  quota    <none>    
pn  xfsdump  <none>    

-- no debconf information


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2012-02-28  7:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28  7:49 Goswin von Brederlow [this message]
2012-02-28  9:11 ` Bug#661580: mkfs.xfs fails to detect correct sector size Christoph Hellwig
2012-02-28 13:28   ` Carlos Maiolino
2012-02-28 19:19   ` Goswin von Brederlow
2012-02-29 19:56   ` Eric Sandeen
2012-03-01  3:53     ` Goswin von Brederlow
2012-03-01  6:06       ` Christoph Hellwig
2012-03-01  8:56         ` Goswin von Brederlow
  -- strict thread matches above, loose matches on Subject: below --
2012-03-01  8:14 Goswin von Brederlow
2012-03-01  8:33 ` Christoph Hellwig
2012-03-01  9:07   ` Goswin von Brederlow
2012-03-01 20:55   ` Eric Sandeen
2012-03-02  5:05     ` 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=20120228074914.31280.78231.reportbug@frosties.localnet \
    --to=goswin-v-b@web.de \
    --cc=661580@bugs.debian.org \
    --cc=submit@bugs.debian.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