We have been talking about this for several weeks now. When you originally brought this
up I asked you to report on the amount of RAM and number of handles which were allocated
under different scenarios. You gave us a report which indicated that when the AFSCache
was filled the memory allocated to afsd_service.exe was slightly above the size of the
cache file and that the number of handles were equal to <cache size> / <block size> plus
a few. The e-mail was dated 12/1 and the actual numbers were 209,608K and 140 handles.
You also provided a scenario which I tested on my systems using the daily builds. The
behavior was in-line with that which you reported. If you have new data to report,
please provide scenarios and numbers which can be replicated in a controlled environment.
Please add this data to the Request (#2628). Be sure to specify exactly which build
of OpenAFS you tested against. (Preferably something very recent due to all of the memory
and handle allocation bugs which have been recently fixed.)
If there is a bug I would like to find it, if there is not I will explain to you why the
behavior is what it is.
Jeffrey Altman
Rodney M Dyer wrote:
Jeffrey,
Ah, tedious to the end eh? No, you are incorrect. The only error made here is that the units that I used in my previous email where wrong. Everywhere I used "Meg", I should have said "K". Using that reasoning...
8192 = 8.192 Meg
So,
8192K / 32K = 256 Handles...Not many at all.
So please explain why the handle count rises into the multiple thousands?
If you had even tried to look at my mail a little closer you should have realized my mistake. An 8192 Meg cache would be 8 Gig. It should be obvious to anyone who has used the Windows version that you can't make a cache over 2 Gig in size. So I was obviously intending the 8 Meg cache. You could have just asked. We've only been discussing this for a couple weeks now, you should have seen that I was meaning a smaller cache than normal.
The bug still stands, unless you can reason a way out of this...
Rodney
smime.p7s
Description: S/MIME Cryptographic Signature
