Description of problem:

posix converts incoming operations on files to operations on
corresponding gfid handles. While this in itself is not a problem,
logging of those gfid handles in place of actual file paths can
create confusions during debugging. The best way would be to
print both the actual file (recieved as an argument) for path
based operations and the gfid handle associated with it.


Ex:

[2019-01-29 08:50:24.373828] E [MSGID: 113039] [posix.c:3122:posix_open] 0-vol_f108aba8b492c40e74247293db9d544a-posix: open on /export/brick/.glusterfs/b8/b4/b8b47498-00df-4ab1-814a-b950250ef598, flags: 0 [No such file or directory]

In the above log, if the actual file path was also mentioned (which posix_open gets as an argument), it would have helped in debugging and analysis better.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: