From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from brick.kernel.dk ([93.163.65.50]:56005 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751729AbZFVR50 (ORCPT ); Mon, 22 Jun 2009 13:57:26 -0400 Date: Mon, 22 Jun 2009 19:57:28 +0200 From: Jens Axboe Subject: Re: unexpected results from simple test? Message-ID: <20090622175728.GK31415@kernel.dk> References: <1245667272.2704.41.camel@localhost.localdomain> <20090622105104.GC31415@kernel.dk> <1245680446.2704.61.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1245680446.2704.61.camel@localhost.localdomain> Sender: fio-owner@vger.kernel.org List-Id: fio@vger.kernel.org To: Richard Kennedy Cc: fio@vger.kernel.org On Mon, Jun 22 2009, Richard Kennedy wrote: > > > In any case, please try and download a new fresh version and see if that > > makes it any better. > > > > There was also a recent linux kernel futex problem that fio triggered, > > so it could also be a kernel issue. Again, knowing what the two other > > jobs are doing would help. > > > Hi Jens, > > 'strace -f' running on a freshly built fio 1.28 > > It runs somewhat slowly but I just get lots of reads & writes like these > > [pid 6597] gettimeofday({1245679454, 899777}, NULL) = 0 > [pid 6597] lseek(8, 419278848, SEEK_SET) = 419278848 > [pid 6597] gettimeofday({1245679454, 899917}, NULL) = 0 > [pid 6597] gettimeofday({1245679454, 899988}, NULL) = 0 > [pid 6597] gettimeofday({1245679454, 900059}, NULL) = 0 > [pid 6597] write(8, "+\265bB\305\243g+\214\313\313\377\20H\237\356\266 > \326X\335<\37\317K\207\317,/\335J\206\267\33"..., 4096) = 4096 > [pid 6597] gettimeofday({1245679454, 900244}, NULL) = 0 > [pid 6597] lseek(8, 419282944, SEEK_SET) = 419282944 > [pid 6597] gettimeofday({1245679454, 900391}, NULL) = 0 > [pid 6597] gettimeofday({1245679454, 900463}, NULL) = 0 > [pid 6597] gettimeofday({1245679454, 900534}, NULL) = 0 > [pid 6597] read(8, "+\265bB\305\243g+\214\313\313\377\20H\237\356\266 > \326X\335<\37\317K\207\317,/\335J\206\267\33"..., 4096) = 4096 > [pid 6597] gettimeofday({1245679454, 900705}, NULL) = 0 > [pid 6597] lseek(8, 419287040, SEEK_SET) = 419287040 > [pid 6597] gettimeofday({1245679454, 900845}, NULL) = 0 > [pid 6597] gettimeofday({1245679454, 900914}, NULL) = 0 > [pid 6597] gettimeofday({1245679454, 900985}, NULL) = 0 > [pid 6597] write(8, "+\265bB\305\243g+\214\313\313\377\20H\237\356\266 > \326X\335<\37\317K\207\317,/\335J\206\267\33"..., 4096) = 4096 > [pid 6597] gettimeofday({1245679454, 901171}, NULL) = 0 > [pid 6597] lseek(8, 419291136, SEEK_SET) = 419291136 > [pid 6597] gettimeofday({1245679454, 901309}, NULL) = 0 > [pid 6597] gettimeofday({1245679454, 901379}, NULL) = 0 > [pid 6597] gettimeofday({1245679454, 901460}, NULL) = 0 > [pid 6597] read(8, "+\265bB\305\243g+\214\313\313\377\20H\237\356\266 > \326X\335<\37\317K\207\317,/\335J\206\267\33"..., 4096) = 4096 > > > where pid 6597 is job f1 > > I'll rebuild my kernel from the latest git, and check that. So it's still running, perhaps the eta is just off. Is write back caching disabled on that drive? -- Jens Axboe