Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: James Vanns <james.vanns@framestore.com>
Cc: fio@vger.kernel.org
Subject: Re: Prevention of full device?
Date: Wed, 3 Jul 2013 09:08:34 +0200	[thread overview]
Message-ID: <20130703070834.GA32428@kernel.dk> (raw)
In-Reply-To: <335085150.31083401.1372779274187.JavaMail.root@framestore.com>

On Tue, Jul 02 2013, James Vanns wrote:
> Hi. In attempting to get a single job to create files before allowing further jobs to perform I/O on them, I cannot
> see how to restrict the sum total of all the files on the device. I wish to create n files ranging in size from i-j
> with a cap of m in total (so the sum of n does not exceed m). For example;
> 
> [file-generator]
> numjobs=1
> create_only=1
> create_on_open=0
> time_based=0
> fill_fs=0
> fill_device=0
> filesize=4k-20m
> size=512m
> nrfiles=256
> fallocate=posix
> fadvise_hint=1
> filename_format=\$filenum.dat
> directory=/tmp/fio
> 
> I'd expect the above to create 256 files ranging from 4k to 20m and a 'du -sh' on /tmp/fio to result in
> 512m. However, it always seems to fill the device! How can I stop this?

It might be a little confusing, but it's actually documented behaviour.
If you set filesize and nrfiles, that dictates the workload size and not
the size= setting. So with the above, you could expect anywhere from 4k
* 256 to 20m * 256 of bytes used. For a normal random distribution of
sizes, you should see around ~2.5GB of data used.

-- 
Jens Axboe


      reply	other threads:[~2013-07-03  7:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <27943043.31081549.1372778944376.JavaMail.root@framestore.com>
2013-07-02 15:34 ` Prevention of full device? James Vanns
2013-07-03  7:08   ` Jens Axboe [this message]

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=20130703070834.GA32428@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=james.vanns@framestore.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox