From: Jens Axboe <jaxboe@fusionio.com>
To: Sebastian Kayser <sebastian@skayser.de>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Inappropriate ioctl error on Solaris with direct=1
Date: Mon, 22 Nov 2010 19:39:23 +0100 [thread overview]
Message-ID: <4CEAB8DB.7040304@fusionio.com> (raw)
In-Reply-To: <20101122150628.GE28050@sebastiankayser.de>
On 2010-11-22 16:06, Sebastian Kayser wrote:
> * Jens Axboe <jaxboe@fusionio.com> wrote:
>> On 2010-11-16 14:14, Sebastian Kayser wrote:
>>> I would like to provide fio packages for Solaris 10 (via opencsw.org).
>>> Building 1.44.2 worked fine, but when running fio with direct=1, it
>>> fails with an ioctl error. Is this to be expected?
>>>
>>> [...]
>>>
>>> # truss -ftopen,ioctl fio --name=test --size=1g --rw=write --filename=foo --runtime=60 --direct=1
>>> ...
>>> 2472: ioctl(1, TCGETA, 0x08045814) = 0
>>> test: (g=0): rw=write, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1
>>> 2472: open64("/tmp/.fio_mutex.psaa1e", O_RDWR|O_CREAT|O_EXCL, 0600) = 8
>>> 2472: open64("/tmp/.fio_mutex.qsaa1e", O_RDWR|O_CREAT|O_EXCL, 0600) = 9
>>> Starting 1 process
>>> test: Laying out IO file(s) (1 file(s) / 1024MB)
>>> 2472: open64("foo", O_WRONLY|O_CREAT, 0644) = 10
>>> 2473: open64("foo", O_RDWR|O_CREAT, 0600) = 7
>>> 2473: ioctl(7, _ION('f', 76, 0), 0x00000001) Err#25 ENOTTY
>>> fio: pid=2473, err=25/file:ioengines.c:404, func=fio_set_odirect, error=Inappropriate ioctl for device
>>
>> Not sure what the situation is on Solaris, but at least on Linux the
>> file system has to support direct IO. What file system do you have on
>> /tmp? Does it work if you place the files somewhere else?
>
> The above test was carried out on ZFS. I now also tested on UFS where
> direct=1 work just fine. Thanks for the pointer, will go out and look
> into the ZFS + direct I/O details. Would it be asked too much to have
> fio emit an error message hinting towards the "FS needs to be direct I/O
> aware" caveat?
Yes it really should. It does on Linux, but it's in different places.
I'll add that to the Solaris bits as well.
>>> On a related note: do you guys have access to Solaris systems? If not, we
>>> do happily provide access to our build farm (Solaris 8/9/10, x86/SPARC,
>>> equipped with gcc3/4 and Sun Studio 11/12) for upstream mainainers [1]. So
>>> just let me know, if this sounds beneficial to you.
>>
>> I used to have a small T2 box on my desk that could boot into Solaris,
>> that's where I did the initial port and testing. But I don't anymore.
>> But to be honest, I would rather rely on someone trusted to tell me that
>> it works on platform XYZ, I just don't have the resources to run a full
>> battery of tests on all the platforms that fio supports every time I do
>> a release.
>
> Understood. Feel free to let us know in case you find yourself in need
> of Solaris access anyway.
Thanks, will do.
--
Jens Axboe
prev parent reply other threads:[~2010-11-22 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 13:14 Inappropriate ioctl error on Solaris with direct=1 Sebastian Kayser
2010-11-17 8:20 ` Jens Axboe
2010-11-22 15:06 ` Sebastian Kayser
2010-11-22 18:39 ` 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=4CEAB8DB.7040304@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=fio@vger.kernel.org \
--cc=sebastian@skayser.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