From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>, 661580@bugs.debian.org
Cc: Debian Bug Tracking System <submit@bugs.debian.org>,
Carlos Maiolino <cmaiolino@redhat.com>,
Goswin von Brederlow <goswin-v-b@web.de>
Subject: Bug#661580: mkfs.xfs fails to detect correct sector size
Date: Wed, 29 Feb 2012 13:56:22 -0600 [thread overview]
Message-ID: <4F4E82E6.3040505@sandeen.net> (raw)
In-Reply-To: <20120228091151.GA24717@infradead.org>
On 2/28/12 3:11 AM, Christoph Hellwig wrote:
> Carlos, didn't you plan to look into this issue?
>
> Goswin, how do you determin that mkfs is still doing unaligned I/O
> when forcing the large sevtor size? Once we set the sector size XFS
> can't do I/O smaller than it.
I did think this was supposed to be working already:
get_topology(&xi, &ft);
if (ft.sectoralign) {
/*
* Older Linux software RAID versions want the sector size
* to match the block size to avoid switching I/O sizes.
* For the legacy libdisk case we thus set the sector size to
* match the block size. For systems using libblkid we assume
* that the kernel is recent enough to not require this and
* ft.sectoralign will never be set.
*/
sectorsize = blocksize;
} else if (!ssflag) {
/*
* Unless specified manually on the command line use the
* advertised sector size of the device.
*/
sectorsize = ft.sectorsize ? ft.sectorsize : XFS_MIN_SECTORSIZE;
}
but it may depend on whether or not it is being built with libblkid support or not...?
I'll try to test it when I have some time, unless Carlos beats me to it.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-29 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 7:49 Bug#661580: mkfs.xfs fails to detect correct sector size Goswin von Brederlow
2012-02-28 9:11 ` Christoph Hellwig
2012-02-28 13:28 ` Carlos Maiolino
2012-02-28 19:19 ` Goswin von Brederlow
2012-02-29 19:56 ` Eric Sandeen [this message]
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=4F4E82E6.3040505@sandeen.net \
--to=sandeen@sandeen.net \
--cc=661580@bugs.debian.org \
--cc=cmaiolino@redhat.com \
--cc=goswin-v-b@web.de \
--cc=hch@infradead.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