I don't have somewhere to try it at the moment, but my guess would be that you're putting your options after the filename - what if you do: lfs setstripe -c 10 iozone.tmp Shawn ________________________________ From: HPDD-discuss [hpdd-discuss-bounces(a)lists.01.org] on behalf of E.S. Rosenberg [esr+hpdd-discuss(a)mail.hebrew.edu] Sent: Sunday, February 23, 2014 11:27 AM To: Alexander I Kulyavtsev Cc: hpdd-discuss(a)lists.01.org Subject: Re: [HPDD-discuss] iozone and lustre On Thu, Feb 20, 2014 at 7:46 PM, Alexander I Kulyavtsev <aik@fnal.gov<mailto:aik@fnal.gov>> wrote: You may want to use iozone in throughput mode, with flag -t. It will use multple writers/readers on the same node. If you wish to use several client nodes, use iozone cluster mode -+m . You need to prepare cluster file to describe file locations. Use file size , data set large enough to "flush" data after write on server, otherwise read rates are "too good" as data read from memory. Try iozone remount option. We used iozone wrapper on slave nodes and set "dont need" flag for the file on write so it is flushed from cache, at least rates changed. You may want to watch rates on network and choose time period when all processes do io. Iozone printout includes period when some procs finished and late starters doing io. But: network rates include retries and read aheads. This is independent of file striping. Thanks Alex I'm going to try that! Sorry that I keep bothering everyone but: How do I troubleshoot lfs setstripe that refuses saying it's getting an invalid argument (22)? lfs setstripe iozone.tmp -c 10 unable to open 'iozone.tmp': Invalid argument (22) error: setstripe: create stripe file 'iozone.tmp' failed I have tried first touching the file, I have tried it on directories (both existing and non-existing) but all the same result. I am running the command as a regular user inside a folder that belongs to the user.... Thanks, Eli Alex On Feb 20, 2014, at 8:01 AM, "E.S. Rosenberg" <esr+hpdd-discuss@mail.hebrew.edu<mailto:esr%2Bhpdd-discuss@mail.hebrew.edu>> wrote:

re:all On Mon, Feb 24, 2014 at 9:48 AM, Cédric Dufour - Idiap Research Institute < cedric.dufour(a)idiap.ch&gt; wrote: We are running the in-kernel client, kernel 3.13.x on Debian machines The lfs utility in use is from the lustre 2.4.2 branch I see that a patch was submitted to the linux-kernel team, does anyone have a link to that patch? I'd like to or patch our kernel or see what version of the kernel we should be building, if it made it into 3.14-rcX then we'll build that... Thanks, Eli

re:all On Tue, Mar 4, 2014 at 4:04 PM, Simmons, James A. <simmonsja(a)ornl.gov&gt;wrote: Correct me if I'm wrong but it looks like that patch hit a dead end... Andreas did any fsdevs ever voice an opinion on generic/lustre flags? Thanks, Eli