public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Brian Hemme <bmh@rincon.com>
Cc: xfs@oss.sgi.com
Subject: Re: mkfs.xfs fails with raid5 and smaller chunk sizes
Date: Wed, 17 Sep 2014 08:17:38 +1000	[thread overview]
Message-ID: <20140916221738.GO4322@dastard> (raw)
In-Reply-To: <5418B39C.2060707@rincon.com>

On Tue, Sep 16, 2014 at 03:03:08PM -0700, Brian Hemme wrote:
> Hello all,
> 
> I am having some odd problems with mkfs.xfs when used on a raid 5
> array.  The array is built from 6 960GB SSDs all connected to SATA
> ports on the MB and created with mdadm.  If I use a chunk size any
> smaller then 512K mkfs.xfs just hangs forever.  It continues to use
> CPU and so does the raid array but never completes.  If the system
> is just left running for an extended length of time the whole OS
> eventually locks up.  I have tried this on three different systems
> with the same results.   I have searched all over for someone with
> similar issues without success.  I am hoping I am just doing
> something clearly wrong and you all can set me straight quickly.
> 
> Some specifics:
>     Arch linux with 3.14.1 kernel
>     mkfs.xfs version 3.1.11
>     mdadm - v3.3 - 3rd September 2013
> 
> Commands:
> > mdadm --create /dev/md0 --chunk=64K --level=5 --raid-devices=6
> /dev/sd[a-f]
> > mkfs.xfs /dev/md0
>   ** This command fails and locks up
> 
> I have tried specifying the arguments to mkfs.xfs with the same
> results.  Building a 4 drive array seems to require a chunk size of
> 1M or greater to work.  Same results if I make a partition on the
> array and make the fs there.

mkfs.xfs really should only take a couple of seconds to complete.
Seeing as you are using SSDs, my first suspicion is that md or the
SSDs are having problems with discard. Hence you should first
try 'mkfs.xfs -K /dev/md0' and see if that completes quickly.

Otherwise, output of 'echo w > sysrq-trigger' from dmesg would be a
good start, as would a 'perf top -G -U' snapshot (run for 30s at
least a minute after mkfs.xfs starts) to tell us what is burning
CPU.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2014-09-16 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 22:03 mkfs.xfs fails with raid5 and smaller chunk sizes Brian Hemme
2014-09-16 22:17 ` Dave Chinner [this message]
2014-09-16 22:47   ` Brian Hemme
2014-09-17  6:02     ` Dave Chinner
2014-09-17 15:06       ` Brian Hemme

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=20140916221738.GO4322@dastard \
    --to=david@fromorbit.com \
    --cc=bmh@rincon.com \
    --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