From: Jens Axboe <axboe@kernel.dk>
To: "Carino, Mario" <Mario.Carino@AIG.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio on AIX - fallocate error
Date: Thu, 10 Apr 2014 10:12:58 -0600 [thread overview]
Message-ID: <5346C30A.30006@kernel.dk> (raw)
In-Reply-To: <E2B4022DB0264A4B90C5F1B01B8E677D73322909@LIVP3MMBX13.mail.aig.net>
On 04/10/2014 09:56 AM, Carino, Mario wrote:
> Here's the job file:
>
> [4ktest]
> fallocate=1
> direct=1
> rw=randwrite
> refill_buffers
> norandommap
> randrepeat=0
> size=2G
> bs=4k
> iodepth=16
> numjobs=16
> runtime=60
> group_reporting
>
> This job file was created based on a sample command line I was given:
>
> fio --filename=/oradata2/o18g2/IO/fiotest4 --direct=1 --rw=randwrite --refill_buffers --norandommap --randrepeat=0 --size=2G --bs=4k --iodepth=16 --numjobs=16 --runtime=60 --group_reporting --name=4ktest
>
> I think I understand enough that I need to run a rw=write job first before running the above job, correct?
No, you should not have to run rw=write first, you can run it as-is and
fio should setup the files appropriately.
Can you try and delete any leftover 4ktest.* files from the job, and
then re-run the job and add --debug=file? Then just break it when it
starts going and send the output in a reply here.
--
Jens Axboe
next prev parent reply other threads:[~2014-04-10 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 2:52 fio on AIX - fallocate error Carino, Mario
2014-04-10 14:00 ` Jens Axboe
2014-04-10 15:07 ` Jens Axboe
2014-04-10 15:30 ` Carino, Mario
2014-04-10 15:34 ` Jens Axboe
2014-04-10 15:56 ` Carino, Mario
2014-04-10 16:12 ` Jens Axboe [this message]
2014-04-10 16:22 ` Carino, Mario
2014-04-10 16:35 ` Jens Axboe
2014-04-10 16:44 ` Carino, Mario
2014-04-10 16:57 ` Jens Axboe
2014-04-10 16:59 ` Carino, Mario
2014-04-10 17:01 ` Jens Axboe
2014-04-10 17:26 ` Carino, Mario
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=5346C30A.30006@kernel.dk \
--to=axboe@kernel.dk \
--cc=Mario.Carino@AIG.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 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.