All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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 10:07:55 +0100	[thread overview]
Message-ID: <87r4xcy9hw.fsf@frosties.localnet> (raw)
In-Reply-To: <20120301083345.GA24409@infradead.org> (Christoph Hellwig's message of "Thu, 1 Mar 2012 03:33:45 -0500")

Christoph Hellwig <hch@infradead.org> writes:

> On Thu, Mar 01, 2012 at 09:14:09AM +0100, Goswin von Brederlow wrote:
>> And I can confirm that the sector size detection is still broken in
>> 3.1.7.
>
> That's a known bug that Carlos wanted to look into.  If you really can't
> accept smaller I/O without major pain make sure to use a larger logical
> blocksize, which should be handled fine by everything.

Tried that too. Setting a locigal block size of 4096 makes all access
aligned to 4096 byte and makes mkfs.xfs detect a sector size of 4096
too.

But that breaks partitioning support for example. Linux simply won't
read the partition table on /dev/nbd0 anymore. Not sure why. Plus that
doesn't solve the problem for real harddisks.

MfG
        Goswin


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

  reply	other threads:[~2012-03-01  9:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01  8:14 Bug#661580: mkfs.xfs fails to detect correct sector size Goswin von Brederlow
2012-03-01  8:33 ` Christoph Hellwig
2012-03-01  9:07   ` Goswin von Brederlow [this message]
2012-03-01 20:55   ` Eric Sandeen
2012-03-02  5:05     ` Eric Sandeen
  -- strict thread matches above, loose matches on Subject: below --
2012-02-28  7:49 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

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=87r4xcy9hw.fsf@frosties.localnet \
    --to=goswin-v-b@web.de \
    --cc=661580@bugs.debian.org \
    --cc=hch@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.