From: Jens Axboe <axboe@kernel.dk>
To: Bruce Cran <bruce@cran.org.uk>
Cc: fio@vger.kernel.org
Subject: Re: Fio 2.0 coming (was "Re: Recent changes")
Date: Sat, 15 Oct 2011 15:59:19 +0200 [thread overview]
Message-ID: <4E9991B7.4050408@kernel.dk> (raw)
In-Reply-To: <07F638D7-A704-409B-B58F-9DEC711A84F3@cran.org.uk>
On 2011-10-15 14:55, Bruce Cran wrote:
>
> On 15 Oct 2011, at 13:44, Jens Axboe wrote:
>
>> Please try current -git, it should work now.
>
> Thanks, it's fixed.
>
> I can crash the client by pressing ctrl-c on the server:
>
>> ./fio -S
> fio: server listening on 0.0.0.0:8765
> and ^C>
> ^^^^ there seems to be a random "and" printed?
>
>> ./fio -C localhost examples/tiobench-example
>
> ...
>
> <muon> f3: Laying out IO file(s) (1 file(s) / 512MB)
> <muon> f3: Laying out IO file(s) (1 file(s) / 512MB)
> <muon> f3: Laying out IO file(s) (1 file(s) / 512MB)
> <muon> f4: Laying out IO file(s) (1 file(s) / 512MB)
> <muon> f4: Laying out IO file(s) (1 file(s) / 512MB)
> <muon> f4: Laying out IO file(s) (1 file(s) / 512MB)
> <muon> f4: Laying out IO file(s) (1 file(s) / 512MB)
> <muon>
> Assertion failed: (cmdret->opcode == cmd.opcode), function fio_net_recv_cmd, file server.c, line 187.
>
> Program received signal SIGABRT, Aborted.
> [Switching to Thread 28301140 (LWP 100220/initial thread)]
> 0x281e7207 in kill () from /lib/libc.so.7
> (gdb) bt
> #0 0x281e7207 in kill () from /lib/libc.so.7
> #1 0x280eb377 in raise () from /lib/libthr.so.3
> #2 0x281e5d3a in abort () from /lib/libc.so.7
> #3 0x281ce0c6 in __assert () from /lib/libc.so.7
> #4 0x08074f8e in fio_net_recv_cmd (sk=3) at server.c:187
> #5 0x08077f95 in fio_handle_clients () at client.c:779
> #6 0x08051033 in exec_run () at fio.c:1779
> #7 0x08051be1 in main (argc=4, argv=0xbfbfec04, envp=Error accessing memory address 0xb: Bad address.
> ) at fio.c:1904
> (gdb)
OK, I'll take a look at that one. You are a good tester :-)
The assert itself is a fragmented packet, where a later fragment does
not match the initial opcode. Must be due to a read error not being
handled correctly.
--
Jens Axboe
next prev parent reply other threads:[~2011-10-15 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 4:00 Recent changes Jens Axboe
2011-10-14 6:20 ` Fio 2.0 coming (was "Re: Recent changes") Jens Axboe
2011-10-14 16:55 ` Bruce Cran
2011-10-15 8:08 ` Jens Axboe
2011-10-15 8:22 ` Jens Axboe
2011-10-15 12:44 ` Jens Axboe
2011-10-15 12:55 ` Bruce Cran
2011-10-15 13:59 ` Jens Axboe [this message]
2011-10-15 14:08 ` Jens Axboe
2011-10-15 14:11 ` Bruce Cran
-- strict thread matches above, loose matches on Subject: below --
2011-10-14 16:43 Martin Steigerwald
2011-10-15 8:07 ` Jens Axboe
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=4E9991B7.4050408@kernel.dk \
--to=axboe@kernel.dk \
--cc=bruce@cran.org.uk \
--cc=fio@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