xfs
[Top] [All Lists]

Re: mkfs.xfs fails with raid5 and smaller chunk sizes

To: Brian Hemme <bmh@xxxxxxxxxx>
Subject: Re: mkfs.xfs fails with raid5 and smaller chunk sizes
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 17 Sep 2014 08:17:38 +1000
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <5418B39C.2060707@xxxxxxxxxx>
References: <5418B39C.2060707@xxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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@xxxxxxxxxxxxx

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