From: Christoph Hellwig <hch@infradead.org>
To: Eryu Guan <eguan@redhat.com>
Cc: linux-xfs@vger.kernel.org, darrick.wong@oracle.com
Subject: Re: [BUG] xfs/109 crashed 2k block size reflink enabled XFS
Date: Mon, 5 Dec 2016 07:36:25 -0800 [thread overview]
Message-ID: <20161205153625.GA20032@infradead.org> (raw)
In-Reply-To: <20161205143906.GA16352@infradead.org>
On Mon, Dec 05, 2016 at 06:39:06AM -0800, Christoph Hellwig wrote:
> On Mon, Dec 05, 2016 at 05:21:12PM +0800, Eryu Guan wrote:
> > Hi,
> >
> > I hit an xfs/109 crash today while testing reflink XFS with 2k block
> > size on x86_64 hosts (both baremetal and kvm guest).
> >
> > It can be reproduced by running xfs/109 many times, I tried 50-times
> > loop twice and it crashed at the 21st and 46th runs. And I can reproduce
> > it with both linus tree (4.9-rc4) and linux-xfs tree for-next branch
> > (updated on 2016-11-30). I haven't been able to reproduce it with 4k
> > block size XFS.
>
> Haven't been able to reproduce it yet unfortunately. But from looking
> at the out of range block this looks like it could be NULLFSBLOCK
> converted to a daddr.
>
> I assume you are running without CONFIG_XFS_DEBUG or CONFIG_XFS_WARN
> enabled?
>
> Below would catch this issue in a non-debug build. Still trying to
> reproduce in the meantime..
Ok, finally managed to reproduce it and hit my BUG_ON below after
hitting the the "trying another AG" printk (only once so far).
Seems like the retry case for COW file systems doesn't work reliably.
That being said given that this tests doesn't even exercise the COW
functionality we shouldn't normally even hit this case, should we?
next prev parent reply other threads:[~2016-12-05 15:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 9:21 [BUG] xfs/109 crashed 2k block size reflink enabled XFS Eryu Guan
2016-12-05 12:45 ` Christoph Hellwig
2016-12-05 14:39 ` Christoph Hellwig
2016-12-05 15:36 ` Christoph Hellwig [this message]
2016-12-05 18:28 ` Darrick J. Wong
2016-12-05 19:05 ` Christoph Hellwig
2016-12-06 6:37 ` Eryu Guan
2016-12-06 14:45 ` Christoph Hellwig
2016-12-06 15:19 ` Brian Foster
2016-12-06 18:14 ` Darrick J. Wong
2016-12-07 3:49 ` Darrick J. Wong
2016-12-07 7:18 ` Christoph Hellwig
2016-12-07 17:40 ` Christoph Hellwig
2016-12-08 6:35 ` Darrick J. Wong
2016-12-08 14:30 ` Christoph Hellwig
2016-12-06 13:48 ` Christoph Hellwig
2016-12-06 15:24 ` Eryu Guan
2016-12-06 16:31 ` 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=20161205153625.GA20032@infradead.org \
--to=hch@infradead.org \
--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