Description of problem: Whenever volume topology changes i.e options are changed/ bricks added or removed, process using libgfapi to access the volume leaks memory. For long running processes like libvirt used to manage guest, this is an issue. Version-Release number of selected component (if applicable): 3.2 How reproducible: NA Steps to Reproduce: NA
The culprits: - Inode table of old graph needs cleanup. Fix inode leaks Fix forget of each xl to free inode ctx properly - The xl objects itself (xlator_t) - The mem_accnt structure in every xl object. Fix all the leaks so that the ref count of mem_accnt structure is 0 - Implement fini() in every xlator
*** Bug 1167648 has been marked as a duplicate of this bug. ***
This is almost 2 years old bug. How relevant is it still?
(In reply to Yaniv Kaul from comment #10) > This is almost 2 years old bug. How relevant is it still? This is still an issue with gfapi access - however not prioritised as RHHI has not made the switch to access via gfapi.
(In reply to Sahina Bose from comment #11) > (In reply to Yaniv Kaul from comment #10) > > This is almost 2 years old bug. How relevant is it still? > > This is still an issue with gfapi access - however not prioritised as RHHI > has not made the switch to access via gfapi. Are we going to move to gfapi? (given the performance gap is not as high as we though initially?). Can we have an intern working on the leaks (can they be seen with ASAN / valgrind)? I wish to reduce the amount of old BZs not being handled.
(In reply to Yaniv Kaul from comment #12) > (In reply to Sahina Bose from comment #11) > > (In reply to Yaniv Kaul from comment #10) > > > This is almost 2 years old bug. How relevant is it still? > > > > This is still an issue with gfapi access - however not prioritised as RHHI > > has not made the switch to access via gfapi. > > Are we going to move to gfapi? (given the performance gap is not as high as > we though initially?). Can we have an intern working on the leaks (can they > be seen with ASAN / valgrind)? > > I wish to reduce the amount of old BZs not being handled. We do not have immediate plans of supporting gfapi. Closing this bz for now, will re-open when we enable gfapi and if we find a problem with memory leak