From: Christoph Hellwig <hch@lst.de>
To: Eryu Guan <eguan@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org, darrick.wong@oracle.com
Subject: Re: [PATCH, RFC] xfs: take indirect blocks into accounting when selecting an AG
Date: Sat, 10 Dec 2016 17:23:24 +0100 [thread overview]
Message-ID: <20161210162324.GB3204@lst.de> (raw)
In-Reply-To: <20161210061641.GQ29149@eguan.usersys.redhat.com>
On Sat, Dec 10, 2016 at 02:16:41PM +0800, Eryu Guan wrote:
> I hit "Internal error xfs_trans_cancel" and force shutdown while running
> xfs/109 in a loop with xfs_2k_reflink test config, first hit at 62nd
> iteration then hit at 32nd iteration. Detailed log appended at the end.
That's the bmap btree insert, so we're still having a problem figuring
out the right indlen somehow.
next prev parent reply other threads:[~2016-12-10 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 17:15 [PATCH, RFC] xfs: take indirect blocks into accounting when selecting an AG Christoph Hellwig
2016-12-09 17:32 ` Darrick J. Wong
2016-12-09 17:41 ` Christoph Hellwig
2016-12-09 21:46 ` Dave Chinner
2016-12-10 16:22 ` Christoph Hellwig
2016-12-10 6:16 ` Eryu Guan
2016-12-10 16:23 ` Christoph Hellwig [this message]
2016-12-10 16:42 ` Christoph Hellwig
2016-12-11 5:19 ` Eryu Guan
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=20161210162324.GB3204@lst.de \
--to=hch@lst.de \
--cc=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/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).