From: Daniel Wagner <wagi@monom.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: Internal error xfs_trans_cancel
Date: Sun, 26 Jun 2016 17:13:33 +0200 [thread overview]
Message-ID: <af4706ea-0129-1692-e354-0bd08fabd255@monom.org> (raw)
In-Reply-To: <a738e82e-ffa5-53e0-ba58-a85a1254baf3@leemhuis.info>
On 06/26/2016 02:16 PM, Thorsten Leemhuis wrote:
> On 02.06.2016 15:29, Daniel Wagner wrote:
>>> Hmmm, Ok. I've been running the lockperf test and kernel builds all
>>> day on a filesystem that is identical in shape and size to yours
>>> (i.e. xfs_info output is the same) but I haven't reproduced it yet.
>> I don't know if that is important: I run the lockperf test and after
>> they have finished I do a kernel build.
>>
>>> Is it possible to get a metadump image of your filesystem to see if
>>> I can reproduce it on that?
>> Sure, see private mail.
>
> Dave, Daniel, what's the latest status on this issue?
I had no time to do some more testing in last couple of weeks. Tomorrow
I'll try to reproduce it again, though last time I tried it couldn't
trigger it.
> It made it to my
> list of know 4.7 regressions after Christoph suggested it should be
> listed. But this thread looks stalled, as afaics nothing happened for
> three weeks apart from Josh (added to CC) mentioning he also saw it. Or
> is this discussed elsewhere? Or fixed already?
The discussion wandered over to the thread called 'crash in xfs in
current' and there are some instruction by Al what to do test
Message-ID: <20160622014253.GS12670@dastard>
cheers,
daniel
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-06-26 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 5:52 Internal error xfs_trans_cancel Daniel Wagner
2016-06-01 7:10 ` Dave Chinner
2016-06-01 13:50 ` Daniel Wagner
2016-06-01 14:13 ` Daniel Wagner
2016-06-01 14:19 ` Daniel Wagner
2016-06-02 0:26 ` Dave Chinner
2016-06-02 5:23 ` Daniel Wagner
2016-06-02 6:35 ` Dave Chinner
2016-06-02 13:29 ` Daniel Wagner
2016-06-26 12:16 ` Thorsten Leemhuis
2016-06-26 15:13 ` Daniel Wagner [this message]
2016-06-14 4:29 ` Josh Poimboeuf
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=af4706ea-0129-1692-e354-0bd08fabd255@monom.org \
--to=wagi@monom.org \
--cc=david@fromorbit.com \
--cc=jpoimboe@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--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