From: Stan Hoeppner <stan@hardwarefreak.com>
To: "Ingo Jürgensmann" <ij@2012.bluespice.org>
Cc: xfs@oss.sgi.com
Subject: Re: mkfs.xfs states log stripe unit is too large
Date: Sun, 24 Jun 2012 17:15:40 -0500 [thread overview]
Message-ID: <4FE7918C.5000203@hardwarefreak.com> (raw)
In-Reply-To: <563739BF-6A66-41F0-8EA2-CF2171E85B06@2012.bluespice.org>
On 6/24/2012 2:51 PM, Ingo Jürgensmann wrote:
> Am 24.06.2012 um 21:28 schrieb Stan Hoeppner:
>
>> Thus, I'd guess that the metadata format changed from 0.90 to 1.2 with a
>> very recent release of mdadm. Are you using distro supplied mdadm, a
>> backported more recent mdadm, or did you build mdadm from the most
>> recent source?
>
> As I already wrote, I'm using Debian unstable, therefore distro supplied mdadm. Otherwise I'd have said this.
Yes, you did mention SID, and I missed it.
SID is the problem here, or I should say, the cause of the error
message. SID is leading (better?) edge, and is obviously using a recent
mdadm release, which defaults to metadata 1.2, and chunk of 512KB.
As more distros adopt newer mdadm, reports of this will be more
prevalent. So Eric's idea is likely preferable than mine. XFS making a
recommendation against an md default would fly like a lead balloon...
> I don't think that Debian unstable is bleeding edge.
It's apparently close enough in the case of mdadm, given you're the
first to report this, AFAIK.
> I find it strange that you've misinterpreted citing the mdadm man page as "sandbagging us". =:-O
Sandbagging simply means holding something back, withholding
information. Had you actually not mentioned your OS/version, this would
have been an accurate take on the situation. But again, youd did, and I
simply missed it. So again, my apologies for missing your mention of
SID in your opening email. That would have prevented my skeptical demeanor.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-06-24 22:15 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 [this message]
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
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=4FE7918C.5000203@hardwarefreak.com \
--to=stan@hardwarefreak.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