On Wed, Aug 05 2009, Jens Axboe wrote: > On Wed, Aug 05 2009, Chris Worley wrote: > > I'm running fio 1.3.1 in Solaris. I'm seeing two issues: > > > > 1) Direct I/O throws an error. > > 2) Performance is way too high. > > > > W/o Direct I/O my size is set to 2.5x memory capacity to assure no > > caching... yet performance for read/write is up to >7x the theoretical > > speed of the storage device (i.e. it's reporting 7GB/s, when > > theoretical for the device is 1GB/s). > > > > I'm not seeing the reporting issue in 1.2.1. > > Are you familiar with git? If yes, then you could try and bisect the > issue. You would do something ala: > > $ git bisect start > $ git bisect good fio-1.21 > $ git bisect bad fio-1.31 > > and then git would checkout a point in between. You would then compile > and run, checking if it works or not. If the version works, then you > would reply with > > $ git bisect good > > if not, then you would do > > $ git bisect bad > > This continues until git tells you which commit is the defective one. > I'll give it a spin on Solaris too, I recently put Solaris 11 on a box > for test purposes. Oh, and if you are not, just wait and I'll double check things here. But please send me your job file(s) so I can reproduce more easily, thanks. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
