>> You might need to install filebench explicitly in /usr/local/filebench >> on Linux to avoid this error...
> That is where it got installed when I ran the make install command. I the above was happening because I did not follow the post installation instruction in the README file properly. Thanks all for all your help. But I am running into newer issues wherein, if I do the following: filebench> load varmail filebench> run 10 filebench> run 10 The first run 10 works fine, but the second one keeps "Waiting for pid ..... thread filereaderthread-1" and then ultimately seems to hang after "running" If I "quit" after the first run and then load again and run again, things work fine. So.... may be am not expected to do "run" twice? Do any of you see such an issue as well? or is it just me doing something wrong? Thank you, John G On Thu, Oct 18, 2007 at 03:13:41PM -0700, John Vijoe George wrote: > Hi, > I am trying to get filebench to run on my Linux ( RHEL 5 ) machine - 2.6.18-8.el5. I managed to install filebench-1.64 successfully, but when I try to run it, I get the following errors: > > filebench> load varmail > 16683: 5.618: Varmail Version 1.24 2005/06/22 08:08:30 personality successfully loaded > 16683: 5.618: Usage: set $dir=<dir> > 16683: 5.618: set $filesize=<size> defaults to 16384 > 16683: 5.618: set $nfiles=<value> defaults to 1000 > 16683: 5.618: set $nthreads=<value> defaults to 16 > 16683: 5.618: set $meaniosize=<value> defaults to 16384 > 16683: 5.618: set $meandirwidth=<size> defaults to 1000000 > 16683: 5.618: (sets mean dir width and dir depth is calculated as log (width, nfiles) > 16683: 5.618: dirdepth therefore defaults to dir depth of 1 as in postmark > 16683: 5.618: set $meandir lower to increase depth beyond 1 if desired) > 16683: 5.618: > 16683: 5.618: run runtime (e.g. run 60) > 16683: 5.618: syntax error, token expected on line 51 > filebench> run 10 > 16683: 7.826: Fileset bigfileset: 1000 files, avg dir = 1000000.0, avg depth = 0.5, mbytes=16 > 16683: 7.843: Removed any existing fileset bigfileset in 1 seconds > 16683: 7.843: Creating fileset bigfileset... > 16683: 7.891: Preallocated 805 of 1000 of fileset bigfileset in 1 seconds > 16683: 7.891: Creating/pre-allocating files > 16683: 7.891: Starting 1 filereader instances > 16683: 7.891: procflow exec proc failed: Permission denied on line 52 > 16683: 32.905: Waiting for process filereader-1 16686 > 16683: 35.906: Waiting for process filereader-1 16686 > 16683: 38.908: Failed to start process filereader-1 > 16683: 38.908: Running... > 16683: 39.911: Run took 1 seconds... > 16683: 39.912: Per-Operation Breakdown > closefile4 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > readfile4 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > openfile4 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > closefile3 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > fsyncfile3 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > appendfilerand3 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > readfile3 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > openfile3 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > closefile2 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > fsyncfile2 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > appendfilerand2 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > createfile2 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > deletefile1 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu > > 16683: 39.912: > IO Summary: 0 ops 0.0 ops/s, (0/0 r/w) 0.0mb/s, 0us cpu/op, 0.0ms latency > 16683: 39.912: Shutting down processes > > > > i have no idea as to why this is happening. Any input is appreciated. > > Regards, > John G > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > _______________________________________________ > perf-discuss mailing list > perf-discuss@opensolaris.org __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
