From: Jens Axboe <axboe@kernel.dk>
To: Urs Schaltegger <urs.schaltegger@itsystems.ch>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio always writes null bytes whatever I do
Date: Tue, 17 Mar 2015 15:56:09 -0600 [thread overview]
Message-ID: <5508A2F9.50701@kernel.dk> (raw)
In-Reply-To: <4471f819ae264ec8bcb6bb1684effd53@keskonrix.itsystems.ch>
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
On 03/12/2015 08:32 AM, Urs Schaltegger wrote:
> fio always writes null bytes whatever I do. I need random data to avoid interference of deduplication solutions (within SSDs or using ZFS).
>
> Windows 8.1 Enterprise x64
>
> fio-2.2.6 (also tried 2.2.0/2.2.1/2.2.3)
>
> fio --section=fiorandom --runtime=60 <FIOFile>
>
> <FIOFile>:
>
> [global]
> ioengine=windowsaio
> thread
> group_reporting
> time_based
> clocksource=clock_gettime
> direct=1
> refill_buffers
> size=1g
> [fiorandom]
> readwrite=randwrite
> numjobs=4
> iodepth=1
> blocksize=8k
> directory=D\:\
Hmm yes, that looks like a regression. Does the attached work?
--
Jens Axboe
[-- Attachment #2: randfill.patch --]
[-- Type: text/x-patch, Size: 465 bytes --]
diff --git a/io_u.c b/io_u.c
index 6567e10a5be2..33b8ac347437 100644
--- a/io_u.c
+++ b/io_u.c
@@ -1895,8 +1895,13 @@ void fill_io_buffer(struct thread_data *td, void *buf, unsigned int min_write,
} while (left);
} else if (o->buffer_pattern_bytes)
fill_buffer_pattern(td, buf, max_bs);
- else
+ else if (o->zero_buffers)
memset(buf, 0, max_bs);
+ else {
+ struct frand_state *rs = get_buf_state(td);
+
+ fill_random_buf(rs, buf, max_bs);
+ }
}
/*
next prev parent reply other threads:[~2015-03-17 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 14:32 fio always writes null bytes whatever I do Urs Schaltegger
2015-03-12 21:05 ` Matthew Eaton
2015-03-17 21:56 ` Jens Axboe [this message]
2015-04-04 2:41 ` Elliott, Robert (Server Storage)
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=5508A2F9.50701@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=urs.schaltegger@itsystems.ch \
/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.