Your message dated Thu, 5 Jan 2017 17:43:38 -0600
with message-id <d82ed44f-4375-fd82-9d81-2ab5e4f8137e@xxxxxxxxxxx>
and subject line close
has caused the Debian Bug report #661580,
regarding mkfs.xfs fails to detect correct sector size
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@xxxxxxxxxxxxxxx
immediately.)
--
661580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661580
Debian Bug Tracking System
Contact owner@xxxxxxxxxxxxxxx with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Package: xfsprogs
Version: 3.1.8
Should be fixed with:
287d168b550857ce40e04b5f618d7eb91b87022f
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Thu, 1 Mar 2012 22:46:35 -0600
Subject: mkfs.xfs: properly handle physical sector size
This splits the fs_topology structure "sectorsize" into
logical & physical, and gets both via blkid_get_topology().
This primarily allows us to default to using the physical
sectorsize for mkfs's "sector size" value, the fundamental
size of any IOs the filesystem will perform.
We reduce mkfs.xfs's "sector size" to logical if
a block size < physical sector size is specified.
This is suboptimal, but permissable.
For block size < sector size, differentiate the error
message based on whether the sector size was manually
specified, or deduced.
Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx>
Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
--- End Message ---
|