From: Dave Chinner <david@fromorbit.com>
To: Daniel Wagner <wagi@monom.org>
Cc: linux-fsdevel@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: Internal error xfs_trans_cancel
Date: Thu, 2 Jun 2016 10:26:53 +1000 [thread overview]
Message-ID: <20160602002653.GL12670@dastard> (raw)
In-Reply-To: <0644b434-6cea-4188-9702-469c26d191b8@monom.org>
On Wed, Jun 01, 2016 at 04:13:10PM +0200, Daniel Wagner wrote:
> >> Anything in the log before this?
> >
> > Just the usual stuff, as I remember. Sorry, I haven't copied the whole log.
>
> Just triggered it again. My steps for it are:
>
> - run all lockperf test
>
> git://git.samba.org/jlayton/lockperf.git
>
> via my test script:
>
> #!/bin/sh
>
> run_tests () {
.....
> for c in `seq 8 32 128`; do
> for l in `seq 100 100 500`; do
> time run_tests "posix01 -n $c -l $l " $DIR/posix01-$c-$l.data
> time run_tests "posix02 -n $c -l $l " $DIR/posix02-$c-$l.data
> time run_tests "posix03 -n $c -l $l " $DIR/posix03-$c-$l.data
> time run_tests "posix04 -n $c -l $l " $DIR/posix04-$c-$l.data
posix03 and posix04 just emit error messages:
posix04 -n 40 -l 100
posix04: invalid option -- 'l'
posix04: Usage: posix04 [-i iterations] [-n nr_children] [-s] <filename>
.....
So I changed them to run "-i $l" instead, and that has a somewhat
undesired effect:
static void
kill_children()
{
siginfo_t infop;
signal(SIGINT, SIG_IGN);
>>>>> kill(0, SIGINT);
while (waitid(P_ALL, 0, &infop, WEXITED) != -1);
}
Yeah, it sends a SIGINT to everything with a process group id. It
kills the parent shell:
$ ./run-lockperf-tests.sh /mnt/scratch/
pid 9597's current affinity list: 0-15
pid 9597's new affinity list: 0,4,8,12
sh: 1: cannot create /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor: Directory nonexistent
posix01 -n 8 -l 100
posix02 -n 8 -l 100
posix03 -n 8 -i 100
$
So, I've just removed those tests from your script. I'll see if I
have any luck with reproducing the problem now.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-06-02 0:26 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 [this message]
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
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=20160602002653.GL12670@dastard \
--to=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wagi@monom.org \
--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;
as well as URLs for NNTP newsgroup(s).