Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1146479

Summary:	[SNAPSHOT]: Need logging correction during the lookup failure case.
Product:	[Community] GlusterFS	Reporter:	Sachin Pandit <spandit>
Component:	snapshot	Assignee:	Sachin Pandit <spandit>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, nsathyan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1174639 (view as bug list)		Environment:
Last Closed:	2015-05-14 17:27:50 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:
Bug Depends On:
Bug Blocks:	1174639

Description Sachin Pandit 2014-09-25 10:22:09 UTC

Description of problem:
When a lookup is issued, and if the entry is not found then snapview-client
will log failure stating that "Lookup on normal graph failed with error Stale file handle". The failure is not in normal graph, hence it requires modification.


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


How reproducible:


Steps to Reproduce:
1. create a gluster volume
2. mount the volume with fuse mount
3. "cd" into ".snaps" directory
4. mkdir "snap999" (assuming snapshot with snapname "snap999" is not present)
5. check the fuse logs

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2014-09-25 11:20:13 UTC

REVIEW: http://review.gluster.org/8851 (USS : Decide the log entry based on the type of graph.) posted (#1) for review on master by Sachin Pandit (spandit)

Comment 2 Anand Avati 2014-09-29 15:13:45 UTC

COMMIT: http://review.gluster.org/8851 committed in master by Vijay Bellur (vbellur) 
------
commit 2736421b26ef03724297b62b4f07ad847c135709
Author: Sachin Pandit <spandit>
Date:   Thu Sep 25 08:32:52 2014 +0530

    USS : Decide the log entry based on the type of graph.
    
    Problem : When a lookup is issued, and if the entry is not found
    then snapview-client will log failure stating that
    "Lookup on normal graph failed with error Stale file handle"
    irrespective of type of graph it received call back from.
    
    Solution : Introduced a check to find out the graph from which
    the snapview-client received call-back.
    
    Change-Id: Iadd5b525c394be3675d40231711058e1cf1396cd
    BUG: 1146479
    Signed-off-by: Sachin Pandit <spandit>
    Reviewed-on: http://review.gluster.org/8851
    Reviewed-by: Raghavendra Bhat <raghavendra>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Niels de Vos 2015-05-14 17:27:50 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Niels de Vos 2015-05-14 17:35:37 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:37:59 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:44:02 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user