From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from merlin.infradead.org ([205.233.59.134]:48700 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965080Ab3E2Iq4 (ORCPT ); Wed, 29 May 2013 04:46:56 -0400 Date: Wed, 29 May 2013 10:46:23 +0200 From: Jens Axboe Subject: Re: FIO 2.1 iops logging problem Message-ID: <20130529084623.GO22724@kernel.dk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: fio-owner@vger.kernel.org List-Id: fio@vger.kernel.org To: "Jeffrey McVay (jmcvay)" Cc: "fio@vger.kernel.org" On Tue, May 28 2013, Jeffrey McVay (jmcvay) wrote: > Hi Jens, > > I cannot seem to get the write_iops_log working with FIO 2.1. > > I found that write_bw_log now requires write_bw_log= to work. > However that does not seem to work on the iops logging. Any idea what > I am doing wrong? Looks like a merge error between fio and gfio, I have fixed it up now. I will be doing a 2.1.1 shortly, since it's not the only one that has cropped up. This is the patch: http://git.kernel.dk/?p=fio.git;a=commit;h=577c83bd488cf3e92d4ccffd39659248bce8ccd3 It has been committed. -- Jens Axboe From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout.micron.com ([137.201.242.129]:54066 "EHLO mailout.micron.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755333Ab3E1VRE convert rfc822-to-8bit (ORCPT ); Tue, 28 May 2013 17:17:04 -0400 Received: from mail.micron.com (ntxboicas01.micron.com [137.201.84.60]) by mailout.micron.com (8.13.6/8.13.6) with ESMTP id r4SLH2YA005722 for ; Tue, 28 May 2013 15:17:02 -0600 From: "Jeffrey McVay (jmcvay)" Subject: RE: FIO 2.1 iops logging problem Date: Tue, 28 May 2013 21:17:01 +0000 Message-ID: Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: fio-owner@vger.kernel.org List-Id: fio@vger.kernel.org To: "fio@vger.kernel.org" Hi Jens, I cannot seem to get the write_iops_log working with FIO 2.1. I found that write_bw_log now requires write_bw_log= to work. However that does not seem to work on the iops logging. Any idea what I am doing wrong? Thanks, Jeff From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: "Jeffrey McVay (jmcvay)" Subject: FIO 2.1 iops logging problem Date: Tue, 28 May 2013 21:01:52 +0000 Message-ID: Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_C8CA972100601A41AE302914E9CE194680367B7ENTXBOIMBX03micr_" MIME-Version: 1.0 To: "fio@vger.kernel.org" Cc: Jens Axboe List-ID: --_000_C8CA972100601A41AE302914E9CE194680367B7ENTXBOIMBX03micr_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Jens, I cannot seem to get the write_iops_log working with FIO 2.1. I found that write_bw_log now requires write_bw_log=3D to work. Howev= er that does not seem to work on the iops logging. Any idea what I am doing= wrong? Thanks, Jeff --_000_C8CA972100601A41AE302914E9CE194680367B7ENTXBOIMBX03micr_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Jens,

 

I cannot seem to get the write_iops_log working with= FIO 2.1.

 

I found that write_bw_log now requires write_bw_log= =3D<text> to work. However that does not seem to work on the iops log= ging. Any idea what I am doing wrong?

 

Thanks,

Jeff

--_000_C8CA972100601A41AE302914E9CE194680367B7ENTXBOIMBX03micr_--