From: Jens Axboe <axboe@kernel.dk>
To: Michael Mattsson <michael.mattsson@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: fio hangs with --status-interval
Date: Thu, 10 Jul 2014 22:07:58 +0200 [thread overview]
Message-ID: <53BEF29E.3040500@kernel.dk> (raw)
In-Reply-To: <CAE56cDvPKq31NrawN_KZF2+eDHiMY2A7azsx8z_DQfG1=-_cnw@mail.gmail.com>
On 2014-07-10 16:55, Michael Mattsson wrote:
> Hey,
> Thanks for the patch. I got log output but I had two clients hanging
> in the same way with the attached patch.
>
> $ patch -p0 < stat.patch
> patching file b/stat.c
> patching file b/stat.h
> Hunk #1 succeeded at 213 (offset -5 lines).
>
> I was using --output <filename>
>
> Worth mentioning here is that on the NFS server the output file is
> written to is issuing a stat(1) on the above output file once per
> second. Could it cause any prolems?
OK, so next question. If you leave it long enough, do you get "stuck
process" dumps from the kernel? In any case, a:
# echo t > /proc/sysrq-trigger
dump would be handy to see for all the fio processes, this doesn't smell
like a fio issue.
--
Jens Axboe
next prev parent reply other threads:[~2014-07-10 20:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 22:56 fio hangs with --status-interval Michael Mattsson
2014-07-10 8:44 ` Jens Axboe
2014-07-10 14:55 ` Michael Mattsson
2014-07-10 20:07 ` Jens Axboe [this message]
2014-07-10 21:27 ` Michael Mattsson
2014-07-11 11:48 ` Jens Axboe
2014-07-11 16:19 ` Michael Mattsson
2014-07-12 8:42 ` Jens Axboe
2014-07-16 16:58 ` Vasily Tarasov
2014-07-21 8:08 ` Jens Axboe
2014-07-21 20:25 ` Vasily Tarasov
2014-07-21 20:54 ` Jens Axboe
2014-07-25 7:43 ` Jens Axboe
2014-07-25 7:56 ` Jens Axboe
2014-07-25 16:34 ` Vasily Tarasov
2014-07-28 8:56 ` Jens Axboe
2014-07-28 16:05 ` Vasily Tarasov
2014-07-28 19:49 ` Jens Axboe
2014-10-23 15:57 ` Michael Mattsson
2014-10-23 16:01 ` Jens Axboe
2014-10-23 21:58 ` Michael Mattsson
2014-10-24 5:17 ` Jens Axboe
2014-10-24 15:33 ` Michael Mattsson
2014-10-24 15:50 ` Jens Axboe
2014-11-04 15:46 ` Vasily Tarasov
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=53BEF29E.3040500@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=michael.mattsson@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.