From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from casper.infradead.org ([85.118.1.10]:49305 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754392Ab2EBMNJ (ORCPT ); Wed, 2 May 2012 08:13:09 -0400 Message-ID: <4FA124B9.8050505@kernel.dk> Date: Wed, 02 May 2012 14:12:41 +0200 From: Jens Axboe MIME-Version: 1.0 Subject: Re: Running fio with offset Increment option References: <4F899663.8050406@kernel.dk> <4F8997E9.6090206@kernel.dk> <4F8D0E1A.2020004@kernel.dk> <4F8FA704.30006@kernel.dk> <4F9101C0.100@kernel.dk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: fio-owner@vger.kernel.org List-Id: fio@vger.kernel.org To: Suresh Dhanarajan Cc: fio@vger.kernel.org On 04/28/2012 09:09 PM, Suresh Dhanarajan wrote: > Hi Jens, > > I verified the offsets by using the write_io_log switch. > when i use offset increment without patch the offset are incremented > and not reset to zero after stone wall. > when i use with patch the offset resets to zero after stone wall. > I hope you are testing with the patch. > If it is so this what the behavior iam also seeing. I'm puzzled. Did a full test here now, with the patch. Simple job: [global] ioengine=null bs=1k size=10m offset_increment=1m numjobs=2 write_iolog=log [job1] rw=read [job2] stonewall rw=read using both the write_iolog and --debug=io, I verified that job1 has two files, one starts at 0M the next at 1M. job2 has two files, one starts at 0M the next at 1M. If I remove the stonewall, job1 has 0M/1M and job has 2M/3M. That certainly looks like it's working to me. I think you need to check and double check that you are indeed using a patched version. And note that write_iolog will _append_ to an existing log file. Perhaps you are looking at an earlier entry set? -- Jens Axboe