Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@permabit.com>
To: fio@vger.kernel.org
Subject: failing to flush cache
Date: Thu, 03 Sep 2015 15:50:38 -0400	[thread overview]
Message-ID: <6eio7rqo35.fsf@just-testing.permabit.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]


I've hit a couple test failures where fio quickly died thusly:

    fio 2.0.7
    Starting 1 thread
    fio: pid=6196, err=11/file:filesetup.c:404, func=invalidate_cache, error=Resource temporarily unavailable

(Yeah, we're a little behind. But I think the relevant code is similar.)

We're testing against Linux (RHEL 6.6) multipath block devices, and it
appears that at the time the fio test starts, the multipath maps for
those devices may still be in flux. I poked around a bit with systemtap,
and it appears that while updating the maps, multipathd "suspends" its
multipath device for a few tens of milliseconds, and the kernel
multipath code rejects ioctl calls with EAGAIN if the device is
suspended. It's a small window, but we've managed to hit it multiple
times, though it's not reliably reproducible.

I know the current sources treat failure here as non-fatal, but if we're
using fio for performance tests, trying a little harder to do the
invalidation seems like a good idea. My approach is to add a retry loop
in __file_invalidate_cache; a patch is attached.

It could also be pushed down into blockdev_invalidate_cache, where it
could be local to the Linux (and Android?) implementation, since none of
the others actually do anything. (They return either EAGAIN or zero,
both of which are taken as success indicators.)

Ken


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: invalidate_cache retry loop --]
[-- Type: text/x-diff, Size: 949 bytes --]

==== //eng/albireo/src/c++/third/fio/filesetup.c#3 - /permabit/user/raeburn/alb-9/src/c++/third/fio/filesetup.c ====
--- /tmp/tmp.32669.54	2015-09-02 20:22:17.000000000 -0400
+++ /permabit/user/raeburn/alb-9/src/c++/third/fio/filesetup.c	2015-09-02 20:21:27.511490391 -0400
@@ -388,7 +388,18 @@
 	} else if (f->filetype == FIO_TYPE_FILE) {
 		ret = posix_fadvise(f->fd, off, len, POSIX_FADV_DONTNEED);
 	} else if (f->filetype == FIO_TYPE_BD) {
+		int retry_count = 0;
 		ret = blockdev_invalidate_cache(f);
+		while (ret < 0 && errno == EAGAIN && retry_count++ < 25) {
+			/*
+			 * Linux multipath devices reject ioctl while
+			 * the maps are being updated. That window can
+			 * last tens of milliseconds; we'll try up to
+			 * a quarter of a second.
+			 */
+			usleep(10000);
+			ret = blockdev_invalidate_cache(f);
+		}
 		if (ret < 0 && errno == EACCES && geteuid()) {
 			if (!root_warn) {
 				log_err("fio: only root may flush block "

             reply	other threads:[~2015-09-03 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 19:50 Ken Raeburn [this message]
2015-09-04 19:29 ` failing to flush cache 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=6eio7rqo35.fsf@just-testing.permabit.com \
    --to=raeburn@permabit.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