From: Jens Axboe <axboe@kernel.dk>
To: Roger Sibert <Roger_Sibert@xyratex.com>
Cc: fio@vger.kernel.org
Subject: Re: segfault runninng fio against 2048 jobs
Date: Wed, 18 Apr 2012 09:23:41 +0200 [thread overview]
Message-ID: <4F8E6BFD.10408@kernel.dk> (raw)
In-Reply-To: <0FEAAA2D70C89D49A62173478A6C4A5D02DECC2A@XYUS-EX22.xyus.xyratex.com>
On 04/17/2012 11:05 PM, Roger Sibert wrote:
> Hello Everyone,
>
> I am using a 2.0x variant ran across a couple of things, one of which
> looks to be as designed and the other was a segfault in fio.
>
> My original job file had 4800 entries which exceeds the max limit.
> (error: maximum number of jobs (2048) reached) The question I have
> here , is there a reason the limit can't be raised to handle larger
> job files?
There's no inherent limit in fio that causes this, it was done to avoid
errors on platforms where shared memory segments were more limited. A
check now reveals that thread_data is around 15KB, which means that the
segment is around 30MB in total. You should be safe to bump the
#define REAL_MAX_JOBS 2048
in fio.h to something bigger. In fact I should just make it bigger, we
scale it down these days if we see errors.
> Reducing the job file to the max re-running it jumped straight to the initial print screen and then to a segfault. (Segmentation fault (core dumped))
>
> Doing a quick look gave me
>
> [root@localhost std-testing]# gdb fio core.9582
> GNU gdb (GDB) CentOS (7.0.1-42.el5.centos)
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /root/fio-test/std-testing/fio...done.
> [New Thread 9583]
> [New Thread 9582]
>
> warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff213fd000
> Core was generated by `./fio --output=1.log 1.inp'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x00000000004167b0 in display_thread_status (je=<value optimized out>) at eta.c:416
> 416 eta.c: No such file or directory.
> in eta.c
> (gdb) quit
>
> I reduced the job count down to about 33 and re-started the run which I am waiting to finish so I can re-compile fio with whatever extra flags and to whatever code level are requested. Currently file gives me:
> fio: ELF 64-bit LSB executable, AMD x86-64, version 1 (GNU/Linux), for GNU/Linux 2.6.15, statically linked, not stripped
> Which is running on a CentOS box
> Linux localhost.localdomain 2.6.18-308.1.1.el5 #1 SMP Wed Mar 7 04:16:51 EST 2012 x86_64 x86_64 x86_64 GNU/Linux
There's not enough information here to help you out, I'm afraid. What
fio version are you running? What job did you run that caused this
failure?
--
Jens Axboe
next prev parent reply other threads:[~2012-04-18 7:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 21:05 segfault runninng fio against 2048 jobs Roger Sibert
2012-04-18 7:23 ` Jens Axboe [this message]
2012-04-18 9:02 ` Roger Sibert
2012-04-18 17:27 ` Roger Sibert
2012-04-18 18:16 ` Roger Sibert
2012-04-18 18:42 ` Jens Axboe
2012-04-18 18:39 ` Jens Axboe
2012-04-18 19:46 ` Roger Sibert
2012-04-20 6:40 ` Jens Axboe
2012-04-20 14:21 ` Roger Sibert
2012-04-20 14:27 ` Jens Axboe
2012-04-20 16:22 ` Steven Lang
2012-04-20 17:22 ` 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=4F8E6BFD.10408@kernel.dk \
--to=axboe@kernel.dk \
--cc=Roger_Sibert@xyratex.com \
--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