From: Eric Sandeen <sandeen@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "Ingo Jürgensmann" <ij@2012.bluespice.org>, xfs@oss.sgi.com
Subject: Re: mkfs.xfs states log stripe unit is too large
Date: Tue, 26 Jun 2012 22:06:28 -0400 [thread overview]
Message-ID: <4FEA6AA4.1@redhat.com> (raw)
In-Reply-To: <20120626023059.GC19223@dastard>
On 6/25/12 10:30 PM, Dave Chinner wrote:
...
> Without the warning, nobody would have noticed this. I think the
> warning has value - even if it is just to indicate MD now uses a
> bad default value for common workloads..
Fair enough.
log stripe unit (524288 bytes) is too large (maximum is 256KiB)
log stripe unit adjusted to 32KiB
It just tweaked me a little to complain about something the user didn't specify, but thinking about it from the perspective of letting the user know that the _device_ has a stripe unit larger than xfs can handle makes sense.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-06-27 2:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 12:50 mkfs.xfs states log stripe unit is too large Ingo Jürgensmann
2012-06-23 23:44 ` Dave Chinner
2012-06-24 2:20 ` Eric Sandeen
2012-06-24 13:05 ` Stan Hoeppner
2012-06-24 13:17 ` Ingo Jürgensmann
2012-06-24 19:28 ` Stan Hoeppner
2012-06-24 19:51 ` Ingo Jürgensmann
2012-06-24 22:15 ` Stan Hoeppner
2012-06-25 5:25 ` Ingo Jürgensmann
[not found] ` <4FE8CEED.7070505@hardwarefreak.com>
2012-06-25 21:18 ` Ingo Jürgensmann
2012-06-24 15:03 ` Ingo Jürgensmann
2012-06-26 2:30 ` Dave Chinner
2012-06-26 8:02 ` Christoph Hellwig
[not found] ` <20120702061827.GB16671@infradead.org>
2012-07-02 6:41 ` NeilBrown
2012-07-02 8:08 ` Dave Chinner
2012-07-09 12:02 ` kedacomkernel
2012-06-26 19:34 ` Ingo Jürgensmann
2012-06-27 2:06 ` Eric Sandeen [this message]
2012-06-25 10:33 ` Ingo Jürgensmann
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=4FEA6AA4.1@redhat.com \
--to=sandeen@redhat.com \
--cc=david@fromorbit.com \
--cc=ij@2012.bluespice.org \
--cc=xfs@oss.sgi.com \
/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