From: Eric Sandeen <sandeen@sandeen.net>
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: Sat, 23 Jun 2012 21:20:32 -0500 [thread overview]
Message-ID: <4FE67970.2030008@sandeen.net> (raw)
In-Reply-To: <20120623234445.GZ19223@dastard>
On 6/23/12 6:44 PM, Dave Chinner wrote:
> On Sat, Jun 23, 2012 at 02:50:49PM +0200, Ingo Jürgensmann wrote:
>> muaddib:~# cat /proc/mdstat
>> Personalities : [raid1] [raid6] [raid5] [raid4]
>> md7 : active raid5 sdf4[3] sdd4[1] sde4[0]
>> 7811261440 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
> .....
>
>> The RAID devices /dev/md0 to /dev/md4 are on my old 3x 1 TB
>> Seagate disks. Anyway, to finally come to the problem, when I try
>> to create a filesystem on the new RAID5 I get the following:
>>
>> muaddib:~# mkfs.xfs /dev/lv/usr
>> log stripe unit (524288 bytes) is too large (maximum is 256KiB)
>> log stripe unit adjusted to 32KiB
...
>
>> So, the question is:
>> - is this a bug somewhere in XFS, LVM or Linux's software RAID
>> implementation?
>
> Not a bug at all.
Dave, I'd suggest that we should remove the warning though, if XFS picks
the wrong defaults and then overrides itself.
Rule of Silence: When a program has nothing surprising to say, it should say nothing.
;)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-06-24 2:20 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 [this message]
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
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=4FE67970.2030008@sandeen.net \
--to=sandeen@sandeen.net \
--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