From: Jens Axboe <axboe@kernel.dk>
To: George Smith <glsmith555@gmail.com>
Cc: fio@vger.kernel.org, bruce@cran.org.uk
Subject: Re: Server mode problems with 2.1.1
Date: Thu, 08 Aug 2013 14:57:59 -0600 [thread overview]
Message-ID: <52040657.208@kernel.dk> (raw)
In-Reply-To: <CAGRFgs1hbS8pT01+w50-iF3sj3b1gCCrf-zSpP0CGhnQ-utgrA@mail.gmail.com>
On 08/06/2013 03:52 PM, George Smith wrote:
> Hello,
>
> I have been using FIO (2.0.15) server mode successfully on Linux
> (CentOS 6) and Windows (2012) for perhaps the last 6 months.
>
> Today I built the new (as of a few days ago) FIO 2.1.1 on Linux, and
> everything seems fine there including server mode (Linux -> Linux).
>
> On Windows (package downloaded from bluestop), however, server mode
> does not seem to work anymore. To be clear, I'm running
>
> fio --client <ip> job
>
> from Linux, to an
>
> fio --server
>
> instance running on Win2012. The client connect hangs, and the server
> on the Windows box spews the following:
>
> fork is not implemented
> waitpid is not implemented
> fio: waitpid: Function not implemented
> waitpid is not implemented
> <repeat of the previous errors until the client or server is killed>
>
> I haven't really debugged this too much, was just wondering if I'm
> missing something major (being relatively new to FIO and this list).
> I'm assuming server mode is still supposed to work in these newer
> releases much the same way that the 2.0.15 I'm using does?
I don't think you are missing anything, I wonder what broke the server
mode on Windows. Bruce, any ideas?
--
Jens Axboe
prev parent reply other threads:[~2013-08-08 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 21:52 Server mode problems with 2.1.1 George Smith
2013-08-08 20:57 ` 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=52040657.208@kernel.dk \
--to=axboe@kernel.dk \
--cc=bruce@cran.org.uk \
--cc=fio@vger.kernel.org \
--cc=glsmith555@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox