public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>, 661580@bugs.debian.org
Cc: Goswin von Brederlow <goswin-v-b@web.de>
Subject: Bug#661580: mkfs.xfs fails to detect correct sector size
Date: Thu, 01 Mar 2012 14:55:40 -0600	[thread overview]
Message-ID: <4F4FE24C.6050304@sandeen.net> (raw)
In-Reply-To: <20120301083345.GA24409@infradead.org>

On 3/1/12 2:33 AM, Christoph Hellwig wrote:
> 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.

Carlos is a bit busy right now, I'll send a patch shortly; want to whip
up an xfstest for this too.

-Eric


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

  parent reply	other threads:[~2012-03-01 20:57 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
2012-03-01 20:55   ` Eric Sandeen [this message]
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=4F4FE24C.6050304@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=661580@bugs.debian.org \
    --cc=goswin-v-b@web.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox