From: Goswin von Brederlow <goswin-v-b@web.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Debian Bug Tracking System <submit@bugs.debian.org>,
Eric Sandeen <sandeen@sandeen.net>,
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: Thu, 01 Mar 2012 09:56:13 +0100 [thread overview]
Message-ID: <8762eo3djm.fsf@frosties.localnet> (raw)
In-Reply-To: <20120301060637.GA28009@infradead.org> (Christoph Hellwig's message of "Thu, 1 Mar 2012 01:06:37 -0500")
Christoph Hellwig <hch@infradead.org> writes:
> On Thu, Mar 01, 2012 at 04:53:32AM +0100, Goswin von Brederlow wrote:
>> I'm asuming libblkid is used, otherwise a sectorsize of 512 would make
>> no sense.
>>
>> It might be that NBD advertises the geometry wrong, as in ft.sectorsize
>> isn't set correctly. That would make that part at least a kernel bug.
>
> Now that I've looked at nbd: I can't find any way to transfer the
> physical or logical block size information to the nbd client. How
> do you try set it on the server?
I don't. The protocol doesn't (yet) have an option for this. There are a
number of new options planed for the new handshake protocol but the nbd
maintainer hasn't had time to implement them yet.
What I do is set the blocksize = 4096 on the nbd-client commandline
knowing that that is what the server expects.
MfG
Goswin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-01 9:00 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
2012-03-01 3:53 ` Goswin von Brederlow
2012-03-01 6:06 ` Christoph Hellwig
2012-03-01 8:56 ` Goswin von Brederlow [this message]
-- 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=8762eo3djm.fsf@frosties.localnet \
--to=goswin-v-b@web.de \
--cc=661580@bugs.debian.org \
--cc=cmaiolino@redhat.com \
--cc=hch@infradead.org \
--cc=sandeen@sandeen.net \
--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