[OpenAFS] Open files dissapear?
Harald Barth
haba@kth.se
Thu, 26 Feb 2009 11:52:50 +0100 (CET)
Thanks for all the data! Did a quick test on my laptop. I consider my
laptop to have "working AFS" ;-)
> Problem is repeatable.
Here too (with client 1.4.5 against server 1.4.7) so we
can eliminate "problem due to recent changes in OpenAFS".
$ ./src/blogbench -d /afs/...test/blogbench/
Frequency = 10 secs
Scratch dir = [/afs/...test/blogbench/]
Spawning 3 writers...
Spawning 1 rewriters...
Spawning 5 commenters...
Spawning 100 readers...
Benchmarking for 30 iterations.
The test will run during 5 minutes.
Nb blogs R articles W articles R pictures W pictures R comments W comments
read(): No such file or directoryread(): No such file or directoryread(): No such file or directoryread(): No such file or directory
>From the blogbench webpage:
> Since some filesystems are unable to manage more than 32k or 64k
> links to the same directory (an example is UFS), you should not
> force the test to run a silly amount of time on these filesystems.
So is blogbench running into the directory size limit of AFS and
ignoring the error code or something like that? If I throttle down
blogbench a bit it does not bail out:
$ ./src/blogbench -c 2 -r 10 -w 2 -i 10 -d /afs/...test/blogbench/
Frequency = 10 secs
Scratch dir = [/afs/...test/blogbench/]
Spawning 2 writers...
Spawning 1 rewriters...
Spawning 2 commenters...
Spawning 10 readers...
Benchmarking for 10 iterations.
The test will run during 1 minutes.
Nb blogs R articles W articles R pictures W pictures R comments W comments
12 15764 672 8215 591 8715 1471
23 36326 611 21185 606 19617 1372
27 25634 302 14719 228 12865 670
37 35388 625 20725 631 17091 1085
41 11578 283 7091 170 6474 609
46 11071 368 7273 403 5718 704
47 1262 56 842 98 1284 106
59 23557 805 14762 544 12034 1236
60 3390 40 1813 83 1523 102
66 11984 319 7592 475 5874 756
Final score for writes: 66
Final score for reads : 3574
I don't know enough of the inner works of blogbench to be able to say more.
Harald.