From: Erwan Velu <erwan@seanodes.com>
To: fio@vger.kernel.org
Subject: Passing argument to both write_bw_log & write_lat_log leads to segfault
Date: Wed, 19 Nov 2008 12:23:21 +0100 [thread overview]
Message-ID: <4923F729.1030200@seanodes.com> (raw)
Using fio 1.23:
[root@max13 tmp]# fio myconfigfile
Segmentation fault (core dumped)
Where myconfigfile is the following:
[global]
bsrange=64k-128k,64k-128k
direct=1
ioengine=libaio
iodepth=2
zonesize=256m
zoneskip=2g
[/dev/exa/g1/v1]
rw=read
write_bw_log read-bw
write_lat_log read-lat
[/dev/exa/g1/v1]
stonewall
rw=write
write_bw_log write-bw
write_lat_log write-lat
Note: removing one or the other parameter to write_*_log reports an error like "Bad option write_lat_log read-lat" but letting both of them segfault.
I did this syntaxe as the man page says :
write_bw_log
If given, write bandwidth logs of the jobs in this file.
I thought that "this file" meant a parameter.
Cheers,
--
Erwan Velu
Pre-Sales Engineer
Seanodes
http://www.seanodes.com
+33 (0)1 41 22 13 83
next reply other threads:[~2008-11-19 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 11:23 Erwan Velu [this message]
2008-11-19 11:28 ` Passing argument to both write_bw_log & write_lat_log leads to segfault Jens Axboe
2008-11-19 15:10 ` Erwan Velu
2008-11-19 15:15 ` Jens Axboe
2008-11-19 15:20 ` 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=4923F729.1030200@seanodes.com \
--to=erwan@seanodes.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox