From: <eliezer@integritech.solutions>
To: 'fio' <fio@vger.kernel.org>
Subject: RE: fio 3.12-27g68af on vmware esxi 6.0 build causing segmentation fault
Date: Sat, 1 Dec 2018 10:40:57 -0600 [thread overview]
Message-ID: <000101d48994$a3239410$e96abc30$@integritech.solutions> (raw)
Hello Folks:
Getting a "segmentation fault" error when running latest fio version
(3.12.27-g68af) on vmware 6.0:
> ./fio --bs=16k --size=10GB --readwrite=randrw --ioengine=posixaio
--filename=test10GB.fio --direct=1 --sync=1 --rwmixread=50 --rwmixwrite=50
--direct=1 --sync=1 --name=testvmw6
testvmw6: (g=0): rw=randrw, bs=(R) 16.0KiB-16.0KiB, (W) 16.0KiB-16.0KiB, (T)
16.0KiB-16.0KiB, ioengine=posixaio, iodepth=1
fio-3.12-27-g68af
Segmentation fault
On the following vmware version:
> vmware -v
VMware ESXi 6.0.0 build-5050593
Using fio version below:
> ./fio -version
fio-3.12-27-g68af
> ./fio --enghelp
Available IO engines:
cpuio
mmap
sync
psync
vsync
pvsync
pvsync2
null
net
netsplice
ftruncate
filecreate
posixaio
falloc
e4defrag
splice
mtd
sg
FIO binary built from Docker using the following Dockerfile (Kudos to Mark
Beierl!)
===
FROM multiarch/alpine:x86_64-v3.6 (--- I also tried v3.8 ---)
RUN apk --no-cache add --update \
git \
alpine-sdk \
coreutils \
linux-headers \
libaio \
libaio-dev \
zlib-dev
RUN git clone http://git.kernel.dk/fio.git fio
RUN cd fio && ./configure --esx
RUN cd fio && EXTFLAGS="-static" make -j $(grep -c ^processor /proc/cpuinfo)
install
===
Do I need to use an older fio version and Dockerfile config to run fio on
vmware 6.0, or is the segmentation error due to something else? Not sure
how to debug this further. Any insight how to debug this further is very
much appreciated.
Regards,
Eliezer
reply other threads:[~2018-12-02 3:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000101d48994$a3239410$e96abc30$@integritech.solutions' \
--to=eliezer@integritech.solutions \
--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