RE: fio signal 11

[Jeff Furlong <jeff.furlong@hgst.com>]

Good point.  Here is the trace:

[New LWP 59231]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `fio --name=test_job --ioengine=libaio --direct=1 --rw=write --iodepth=32'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000000000421e39 in regrow_log (iolog=0x7f828c0c5ad0) at stat.c:1909
1909		if (!cur_log) {
 
(gdb) bt
#0  0x0000000000421e39 in regrow_log (iolog=0x7f828c0c5ad0) at stat.c:1909
#1  0x000000000042d4df in regrow_logs (td=td@entry=0x7f8277de0000) at stat.c:1965
#2  0x000000000040ca90 in wait_for_completions (td=td@entry=0x7f8277de0000, time=time@entry=0x7fffcfb6b300) at backend.c:446
#3  0x000000000045ade7 in do_io (bytes_done=<synthetic pointer>, td=0x7f8277de0000) at backend.c:991
#4  thread_main (data=data@entry=0x264d450) at backend.c:1667
#5  0x000000000045cfec in run_threads (sk_out=sk_out@entry=0x0) at backend.c:2217
#6  0x000000000045d2cd in fio_backend (sk_out=sk_out@entry=0x0) at backend.c:2349
#7  0x000000000040d09c in main (argc=22, argv=0x7fffcfb6f638, envp=<optimized out>) at fio.c:63

Regards,
Jeff


-----Original Message-----
From: Sitsofe Wheeler [mailto:sitsofe@gmail.com] 
Sent: Friday, June 10, 2016 12:17 AM
To: Jeff Furlong <jeff.furlong@hgst.com>
Cc: fio@vger.kernel.org
Subject: Re: fio signal 11

On 9 June 2016 at 22:58, Jeff Furlong <jeff.furlong@hgst.com> wrote:
>
> Using the latest version from git, I am getting a signal 11 error when running some workloads.  It may be that workloads fail when we wrap around the device capacity (e.g. runtime and time_based).  See below example parameters:
>
> # fio --name=test_job --ioengine=libaio --direct=1 --rw=write 
> --iodepth=32 --size=100% --numjobs=1 --bs=1m --filename=/dev/nvme0n1 
> --group_reporting --write_bw_log=test_job --write_iops_log=test_job 
> --write_lat_log=test_job --log_avg_msec=1000 --disable_lat=0 
> --disable_clat=0 --disable_slat=0 --runtime=1500s --time_based 
> --ramp_time=5s --output=test_job
>
> fio-2.11-17-ga275
> Starting 1 process
> fio: pid=145763, got signal=11

Could you run fio under gdb (
gdb ./fio
run --name=test_job --ioengine=libaio etc.
)

and when it crashes get a backtrace with thread apply all bt ?

--
Sitsofe | http://sucs.org/~sits/
Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:

This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.