linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: Sitsofe Wheeler <sitsofe@gmail.com>, linux-xfs@vger.kernel.org
Subject: Re: Tasks blocking forever with XFS stack traces
Date: Tue, 5 Nov 2019 12:58:57 +0100	[thread overview]
Message-ID: <20191105115857.5acumcghqzanwh2i@orion> (raw)
In-Reply-To: <20191105103652.n5zwf6ty3wvhti5f@orion>

Just to make clear my previous point:


> > > What's your filesystem configuration? (xfs_info <mount point>)
> > 
> > meta-data=/dev/md126             isize=512    agcount=32, agsize=43954432 blks
> >          =                       sectsz=4096  attr=2, projid32bit=1
> >          =                       crc=1        finobt=1 spinodes=0 rmapbt=0
> >          =                       reflink=0
> > data     =                       bsize=4096   blocks=1406538240, imaxpct=5
> >          =                       sunit=128    swidth=768 blks
> 
> > naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
> > log      =internal               bsize=4096   blocks=521728, version=2
> >          =                       sectsz=4096  sunit=1 blks, lazy-count=1
> 						^^^^^^  This should have been
> 							configured to 8 blocks, not 1
> 

8 blocks here considering you've used default configuration, i.e. XFS defaults
log stripe unit to 32KiB when the device strip is larger than 256KiB.

-- 
Carlos


  reply	other threads:[~2019-11-05 11:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05  7:27 Tasks blocking forever with XFS stack traces Sitsofe Wheeler
2019-11-05  8:54 ` Carlos Maiolino
2019-11-05  9:32   ` Sitsofe Wheeler
2019-11-05 10:36     ` Carlos Maiolino
2019-11-05 11:58       ` Carlos Maiolino [this message]
2019-11-05 14:12       ` Sitsofe Wheeler
2019-11-05 16:09         ` Carlos Maiolino
2019-11-07  0:12         ` Chris Murphy
2019-11-13 10:04       ` Sitsofe Wheeler
2020-12-23  8:45         ` Sitsofe Wheeler

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=20191105115857.5acumcghqzanwh2i@orion \
    --to=cmaiolino@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sitsofe@gmail.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;
as well as URLs for NNTP newsgroup(s).