Bug 1675076

Summary:	[posix]: log the actual path wherever possible
Product:	[Community] GlusterFS	Reporter:	Raghavendra Bhat <rabhat>
Component:	posix	Assignee:	bugs <bugs>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-14 08:29:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raghavendra Bhat 2019-02-11 19:22:36 UTC

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:

Comment 1 Worker Ant 2019-02-14 08:29:33 UTC

REVIEW: https://review.gluster.org/22192 (storage/posix: print the actual file path) merged (#3) on master by Amar Tumballi