From: Jens Axboe <jaxboe@fusionio.com>
To: Nikolaus Jeremic <nikolaus.jeremic@uni-rostock.de>
Cc: fio@vger.kernel.org
Subject: Re: fio causes segfault after particular of random writes
Date: Fri, 24 Sep 2010 08:57:08 +0200 [thread overview]
Message-ID: <4C9C4BC4.9020503@fusionio.com> (raw)
In-Reply-To: <4C9B4A53.1080302@uni-rostock.de>
On 2010-09-23 14:38, Nikolaus Jeremic wrote:
> Hello,
>
> I am using fio for benchmarking of SSDs and noticed that fio causes a
> segfault after writing about 260000 MB with block size of 4069 bytes
> at random in one job. Writing the same or just bigger amount of data
> sequentially in 1 MB blocks works well. The situation is reproducible
> with several fio versions, i.e. 1.34, 1.41, 1.43, 1.43.2 as of
> 09/16/2010.
That's not good. To help me with this, please do:
- Edit the Makefile in fio, remove the -O2 in there.
- make clean && make
- Run ulimit -c10000000000 or something large like that
- Now reproduce the problem. Fio will segfault again, and produce
a core file.
- compress the fio executable and core file and send them to me.
--
Jens Axboe
next prev parent reply other threads:[~2010-09-24 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 12:38 fio causes segfault after particular of random writes Nikolaus Jeremic
2010-09-24 6:57 ` Jens Axboe [this message]
2010-09-24 8:09 ` 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=4C9C4BC4.9020503@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=fio@vger.kernel.org \
--cc=nikolaus.jeremic@uni-rostock.de \
/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