All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Georg Schönberger" <gschoenberger@thomas-krenn.com>
Cc: fio@vger.kernel.org
Subject: Re: write_iops_log/write_bw_log command line parameter bug
Date: Thu, 22 Aug 2013 11:09:57 -0600	[thread overview]
Message-ID: <521645E5.8010509@kernel.dk> (raw)
In-Reply-To: <1314394180.368686.1377164275463.JavaMail.root@thomas-krenn.com>

On 08/22/2013 03:37 AM, Georg Schönberger wrote:
> Hi Jens,
> 
> it seems that the command line options "write_iops_log" and "write_bw_log" don't work as they are described in the man page:
> "If no filename is given with this option, the default filename of "jobname_type.log" is used."
> 
> Unfortunately the files/filenames are not created automatically by fio:
> # fio --name=test --direct=1 --refill_buffers --filesize=1G --bs=8k --rw=randread --ioengine=libaio --runtime=60 --write_iops_log --write_bw_log
> [...]
> # ls
> lost+found  test.1.0  --write_bw_log_iops.log
> 
> If I specify the filenames everything is fine:
> # rm ./--write_bw_log_iops.log
> # fio --name=test --direct=1 --refill_buffers --filesize=1G --bs=8k --rw=randread --ioengine=libaio --runtime=60 --write_iops_log=rr-iops --write_bw_log=rr-bw
> [...]
> # ls
> lost+found  rr-bw_bw.log  rr-iops_iops.log  test.1.0
> 
> I am using fio version fio-2.1.2-13-g3e10.

Don't think there's an easy way to fix this, outside of requiring some
name being set. Arguably that should probably be the way that it functions.

-- 
Jens Axboe


      reply	other threads:[~2013-08-22 17:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <112541105.368381.1377163637545.JavaMail.root@thomas-krenn.com>
2013-08-22  9:37 ` write_iops_log/write_bw_log command line parameter bug Georg Schönberger
2013-08-22 17:09   ` 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=521645E5.8010509@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=gschoenberger@thomas-krenn.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.