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? 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 Thanks, Roger -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
