From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: References: <5669B23C.1020001@kernel.dk> <20151210181540.GB21415@kernel.dk> <5669C364.9020100@kernel.dk> <5669C46F.3090300@kernel.dk> <566AECA3.6000108@kernel.dk> Date: Fri, 11 Dec 2015 23:32:09 +0300 Message-ID: Subject: Re: Exit all jobs on error From: Andrey Kuzmin Content-Type: multipart/alternative; boundary=089e010d8b02b852910526a5375b To: Sitsofe Wheeler Cc: fio@vger.kernel.org, Jens Axboe List-ID: --089e010d8b02b852910526a5375b Content-Type: text/plain; charset=UTF-8 On Dec 11, 2015 22:59, "Sitsofe Wheeler" wrote: > > On 11 December 2015 at 15:32, Jens Axboe wrote: > > On 12/11/2015 03:01 AM, Andrey Kuzmin wrote: > >> > >> ^Cbs: 1 (f=1): [w(1)] [0.0% done] [0KB/0KB/0KB /s] [0/0/0 iops] [eta > >> 01d:12h:24m:29s] > >> Program received signal SIGINT, Interrupt. > >> 0x00007ffff6b7ff3d in nanosleep () at > >> ../sysdeps/unix/syscall-template.S:81 > >> 81 ../sysdeps/unix/syscall-template.S: No such file or directory. > >> (gdb) bt > >> #0 0x00007ffff6b7ff3d in nanosleep () at > >> ../sysdeps/unix/syscall-template.S:81 > >> #1 0x00007ffff6bb14a4 in usleep (useconds=) at > >> ../sysdeps/unix/sysv/linux/usleep.c:32 > >> #2 0x000000000045a7ed in do_usleep (usecs=10000) at backend.c:1951 > >> #3 0x000000000045b33c in run_threads () at backend.c:2216 > >> #4 0x000000000045b6a8 in fio_backend () at backend.c:2333 > >> #5 0x00000000004991cb in main (argc=4, argv=0x7fffffffdda8, > >> envp=0x7fffffffddd0) at fio.c:60 > > > > > > That's not one of the IO threads, that's the main thread. It'll sit and wait > > in that loop until jobs finish. You'll need the backtrace of one of the > > stuck IO thread instead, this trace is quite normal and expected of backend. > > > > -- > > Jens Axboe > > > > Andrey: > > Could you try > thread apply all bt full > (found over on https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces > )? > That test case is already gone, but - if interested - you can easily simulate it by randomly dropping an io_u inside the engine. Regards, Andrey > > -- > Sitsofe | http://sucs.org/~sits/ --089e010d8b02b852910526a5375b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Dec 11, 2015 22:59, "Sitsofe Wheeler" <sitsofe@gmail.com> wrote:
>
> On 11 December 2015 at 15:32, Jens Axboe <axboe@kernel.dk> wrote:
> > On 12/11/2015 03:01 AM, Andrey Kuzmin wrote:
> >>
> >> ^Cbs: 1 (f=3D1): [w(1)] [0.0% done] [0KB/0KB/0KB /s] [0/0/0 i= ops] [eta
> >> 01d:12h:24m:29s]
> >> Program received signal SIGINT, Interrupt.
> >> 0x00007ffff6b7ff3d in nanosleep () at
> >> ../sysdeps/unix/syscall-template.S:81
> >> 81 ../sysdeps/unix/syscall-template.S: No such file or direct= ory.
> >> (gdb) bt
> >> #0=C2=A0 0x00007ffff6b7ff3d in nanosleep () at
> >> ../sysdeps/unix/syscall-template.S:81
> >> #1=C2=A0 0x00007ffff6bb14a4 in usleep (useconds=3D<optimiz= ed out>) at
> >> ../sysdeps/unix/sysv/linux/usleep.c:32
> >> #2=C2=A0 0x000000000045a7ed in do_usleep (usecs=3D10000) at b= ackend.c:1951
> >> #3=C2=A0 0x000000000045b33c in run_threads () at backend.c:22= 16
> >> #4=C2=A0 0x000000000045b6a8 in fio_backend () at backend.c:23= 33
> >> #5=C2=A0 0x00000000004991cb in main (argc=3D4, argv=3D0x7ffff= fffdda8,
> >> envp=3D0x7fffffffddd0) at fio.c:60
> >
> >
> > That's not one of the IO threads, that's the main thread.= It'll sit and wait
> > in that loop until jobs finish. You'll need the backtrace of = one of the
> > stuck IO thread instead, this trace is quite normal and expected = of backend.
> >
> > --
> > Jens Axboe
> >
>
> Andrey:
>
> Could you try
> thread apply all bt full
> (found over on https://wiki.gentoo.org/wiki/Project:Quality_Assuran= ce/Backtraces
> )?
>

That test case is already gone, but - if interested - you ca= n easily simulate it by randomly dropping an io_u inside the engine.

Regards,
Andrey

>
> --
> Sitsofe | http://sucs.org/~sits/

--089e010d8b02b852910526a5375b--