[Gluster-devel] Debugging enhancements for inode/entry lks

Pranith Kumar K pkarampu at redhat.com
Tue Feb 26 09:50:04 UTC 2013

         From discussions with avati, we are thinking of addressing the 
following issues in locks xlator.
         At the moment to find which mount performed inode/entry lks, 
the process needs to be attached to gdb and the connection address needs 
to be de-referenced to figure out the actual owner. We need to move away 
from this model to a model which prints a free form string which 
contains information about the mount which performed the inode/entry lk 
in state-dumps. We also want to print a free-form string which captures 
brief info of the fop that issued the lock.

         Please feel free to add any suggestions you have.


More information about the Gluster-devel mailing list