<div dir="auto">Filtering the brick logs in TRACE mode with rpcsvc.c does show the FOPS.<div dir="auto"><br></div><div dir="auto">From this, I've realized that LOOKUP is actually dns lookup. This actually differs from NFS lookup operation. Please correct me if I'm wrong.</div><div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Jeevan.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Nov 13, 2017 9:40 PM, "Jeevan Patnaik" <<a href="mailto:g1patnaik@gmail.com">g1patnaik@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Hi,<div dir="auto"><br></div><div dir="auto">Can I get a brief description of all the FOPS in gluster or the location of the source code file so that I will try to get an understanding myself?</div><div dir="auto"><br></div><div dir="auto">Few FOPS I'm not clear like FORGET, UNLINK, FLUSH, LOOKUP</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Or is there a way I can tunnel through the FOPS that that are happening in the background for each operation? I have tried this to find from a brick logfile in TRACE mode, but there are way too many calls, but are in form of some system calls but not FOPS.</div><div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Jeevan.</div><div dir="auto"><br></div><div dir="auto"><br></div></div>
</blockquote></div></div>