From: Goswin von Brederlow <goswin-v-b@web.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Debian Bug Tracking System <submit@bugs.debian.org>,
Carlos Maiolino <cmaiolino@redhat.com>,
661580@bugs.debian.org, Goswin von Brederlow <goswin-v-b@web.de>
Subject: Bug#661580: mkfs.xfs fails to detect correct sector size
Date: Tue, 28 Feb 2012 20:19:54 +0100 [thread overview]
Message-ID: <87399ug3z9.fsf@frosties.localnet> (raw)
In-Reply-To: <20120228091151.GA24717@infradead.org> (Christoph Hellwig's message of "Tue, 28 Feb 2012 04:11:51 -0500")
Christoph Hellwig <hch@infradead.org> writes:
> 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'm writing a nbd-server that uses async IO via libaio (the linux kernel
AIO interface). This has some alignment requirements so I set nbd to use
a 4k blocksize and added asserts that all requests are page aligned
(both offset and size of the request). That worked fine for dd and
mkfs.ext4 but fails on mount in general or mkfs.xfs.
So next I added a printf("WARNING: unaligned read/write") and handled
unaligned access in the server to see how extensive the problem is. With
ext4 I get ONE single read request of 512 Byte on mount and everything
else properly 4k aligned. With xfs I get a ton of them.
If you want I can add a log of the read/write requests a mkfs.xfs and
mount generates.
MfG
Goswin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-28 19:54 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 [this message]
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=87399ug3z9.fsf@frosties.localnet \
--to=goswin-v-b@web.de \
--cc=661580@bugs.debian.org \
--cc=cmaiolino@redhat.com \
--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