Lukas, Dan, Are you sure that its a leak of io-cache? did you try by removing the translator and not observe the leak? What made you conclude that cache-size option was being ignored? It could be a memory leak by io-cache at some other place too. I tried to make io-cache memleak, but its not happening, what operations do you guys do to see the leak? can you see if some simple test case makes it leak? (so that it will be easy for me to reproduce the bug here and fix it) Thanks! Krishna On Wed, Nov 5, 2008 at 11:38 PM, Dan Parsons <dparsons@xxxxxxxx> wrote: > Lukas, just to confirm your findings, I have the exact same problem and > reported it about 2 months ago. Just like you, when all my stuff was running > under 32-bit, it wasn't an issue because of the 2GB limit, but now that I'm > using 64-bit for everything, it is a potential system crashing bug. > > > Dan Parsons > > > On Nov 5, 2008, at 1:05 AM, Lukas Hejtmanek wrote: > >> Hello, >> >> On Tue, Nov 04, 2008 at 12:37:03PM +0530, Krishna Srinivas wrote: >>> >>> We want to reproduce the leak in our setup to fix it. What is your >>> setup on the client side? How many servers do you have? What are the >>> applications you run on the mount point? Do you observe leak only when >>> "certain" operations are done? (I am just looking for more clues) >> >> upon my investigation, it seems that the io-cache translator ignores the >> cache >> size config option and on 64bit systems is can easily eat whole memory. On >> 32bit, it usually fails to mmap additional data due to 2GB limit to >> process >> address space. >> >> -- >> Lukáš Hejtmánek >> >> >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@xxxxxxxxxx >> http://lists.nongnu.org/mailman/listinfo/gluster-devel >> > >
