xfs
[Top] [All Lists]

Re: mkfs.xfs states log stripe unit is too large

To: <stan@xxxxxxxxxxxxxxxxx>
Subject: Re: mkfs.xfs states log stripe unit is too large
From: Ingo Jürgensmann <ij@xxxxxxxxxxxxxxxxxx>
Date: Mon, 25 Jun 2012 07:25:06 +0200
Cc: <xfs@xxxxxxxxxxx>
In-reply-to: <4FE7918C.5000203@xxxxxxxxxxxxxxxxx>
Organization: Windfluechter.net
References: <D3F781FA-CEB0-4896-9441-772A9E533354@xxxxxxxxxxxxxxxxxx> <20120623234445.GZ19223@dastard> <4FE67970.2030008@xxxxxxxxxxx> <4FE710B7.5010704@xxxxxxxxxxxxxxxxx> <4954261F-D4FB-4589-BE18-2BFCEC05E9B4@xxxxxxxxxxxxxxxxxx> <4FE76A50.2010902@xxxxxxxxxxxxxxxxx> <563739BF-6A66-41F0-8EA2-CF2171E85B06@xxxxxxxxxxxxxxxxxx> <4FE7918C.5000203@xxxxxxxxxxxxxxxxx>
User-agent: RoundCube Webmail/0.2.2
On 2012-06-25 00:15, Stan Hoeppner wrote:

As I already wrote, I'm using Debian unstable, therefore distro supplied mdadm. Otherwise I'd have said this.
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...

Actually, even man page of Debian stable (Squeeze) mentions:

       -c, --chunk=
Specify chunk size of kibibytes. The default when creating an array is 512KB. To ensure compatibility with earlier versions, the default when Building and array with no persis‐ tent metadata is 64KB. This is only meaningful for RAID0, RAID4, RAID5, RAID6, and
              RAID10.

So, the question is: why did mdadm choose 1.2 format superblock this time? My guess is, that's because of GPT labelled disks instead of MBR, but it's only a guess. Maybe it's because the new md device is bigger in size. All of my other md devices on MBR labelled disks do have 0.90 format superblock, all md devices on the GPT disks are of 1.2 format. Although it doesn't seem a new default in mdadm for me, your assumption would still stand if the cause would turn out to be the GPT label. More and more people will start using GPT labelled disks.

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.

Are ok, I misread "sandboxing us" as "boxing onto us like at a sandbox". So, my apologies here. :-)

--
Ciao...          //    Fon: 0381-2744150
.     Ingo     \X/     http://blog.windfluechter.net

gpg pubkey: http://www.juergensmann.de/ij_public_key.

<Prev in Thread] Current Thread [Next in Thread>