From: Jens Axboe <axboe@kernel.dk>
To: Vikram Seth <seth.vik@gmail.com>
Cc: "Georg Schönberger" <gschoenberger@thomas-krenn.com>,
fio@vger.kernel.org
Subject: Re: Tell fio to only lay out files
Date: Wed, 09 May 2012 22:53:56 +0200 [thread overview]
Message-ID: <4FAAD964.2020504@kernel.dk> (raw)
In-Reply-To: <CAKa9NmuiOhT1+9ze2242w3pYVGLAH4Gbry2sq5vz9hW135TL3g@mail.gmail.com>
On 2012-05-09 22:52, Vikram Seth wrote:
> On Wed, May 2, 2012 at 5:25 AM, Georg Sch�nberger
> <gschoenberger@thomas-krenn.com> wrote:
>> Am 2012-05-02 14:15, schrieb Jens Axboe:
>>> On 05/02/2012 02:12 PM, Georg Sch�nberger wrote:
>>>> Same error after a clean compilation.
>>>> $ fio --version
>>>> fio-2.0.7-13-g3b7f
>>>> $ fio --create_only --name=test-read-4k-4G-1-jobs --directory=./tests
>>>> --rw=read --size=10M --bs=4k --numjobs=4
>>>> max value out of range: 4 (1 max)
>>>> max value out of range: 4 (1 max)
>>> Please don't top post, reply beneath what you are replying to.
>>>
>>> Parser looks confused, because you forgot to add the value for the
>>> create_only option. If you use --create_only=1 instead, it should work.
>>>
>>> I wonder why that isn't caught in the command line variant, if you put
>>> it in a job file it does catch it:
>>>
>>> axboe@nelson:/home/axboe/git/fio $ ./fio seq-null
>>> Option create_only requires an argument
>>> fio: failed parsing create_only
>>> fio: job global dropped
>>>
>>> I'll take a look at that separately.
>>>
>> That works now:
>> $ fio --create_only=1 --name=test --directory=./tests --rw=read
>> --size=10M --bs=4k --numjobs=4
>> test: (g=0): rw=read, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1
>> ...
>> test: (g=0): rw=read, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1
>> fio-2.0.7-13-g3b7f
>> Starting 4 processes
>> test: Laying out IO file(s) (1 file(s) / 10MB)
>> test: Laying out IO file(s) (1 file(s) / 10MB)
>> test: Laying out IO file(s) (1 file(s) / 10MB)
>> test: Laying out IO file(s) (1 file(s) / 10MB)
>>
>>
>> Run status group 0 (all jobs):
>> $ ls tests/
>> test.1.0 test.2.0 test.3.0 test.4.0
>>
>> Nice!
>> Thanks, Georg
>>
>> P.S.: Sorry for top posting
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe fio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Hi Jens,
>
> Does this mean that if we create the files with appropriate names and
> size before starting fio, then fio will not lay them out explicitly?
> Just confirming .. this will be very useful (reduce runtime) when
> performing tests on large filesystems.
It does, yes, or you can just use this create_only option for the same
effect.
Fio uses repeatable file names, it always has.
--
Jens Axboe
next prev parent reply other threads:[~2012-05-09 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 9:15 Tell fio to only lay out files Georg Schönberger
2012-05-02 10:35 ` Jens Axboe
2012-05-02 11:51 ` Georg Schönberger
2012-05-02 11:55 ` Jens Axboe
2012-05-02 12:06 ` Georg Schönberger
2012-05-02 12:08 ` Jens Axboe
2012-05-02 12:12 ` Georg Schönberger
2012-05-02 12:15 ` Jens Axboe
2012-05-02 12:25 ` Georg Schönberger
2012-05-09 20:52 ` Vikram Seth
2012-05-09 20:53 ` Jens Axboe [this message]
2012-05-09 22:10 ` Vikram Seth
2012-05-09 23:49 ` 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=4FAAD964.2020504@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=gschoenberger@thomas-krenn.com \
--cc=seth.vik@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.