Bug 814666 - client3_1-fops.c: Log enhancements
Summary: client3_1-fops.c: Log enhancements
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: pre-release
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
Assignee: GlusterFS Bugs list
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-20 11:13 UTC by Sachidananda Urs
Modified: 2014-04-17 11:38 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.5.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-17 11:38:32 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Sachidananda Urs 2012-04-20 11:13:14 UTC
The path mentioned in the below logs says: <gfid:fed32419-4222-4bb2-a8b7-e036df090dfd>/linux-3.2.11

Should be fixed to print the path.


[2012-04-20 03:39:25.299323] W [client3_1-fops.c:2610:client3_1_lookup_cbk] 0-nfs-test-big-client-3: remote operation failed: Stale NFS file handle. Path: <gfid:fed32419-4222-4bb2-a8b7-e036df090dfd>/linux-3.2.11
[2012-04-20 03:39:25.299617] W [client3_1-fops.c:2610:client3_1_lookup_cbk] 0-nfs-test-big-client-2: remote operation failed: Stale NFS file handle. Path: <gfid:fed32419-4222-4bb2-a8b7-e036df090dfd>/linux-3.2.11
[2012-04-20 03:39:25.299659] W [client3_1-fops.c:2610:client3_1_lookup_cbk] 0-nfs-test-big-client-1: remote operation failed: Stale NFS file handle. Path: <gfid:fed32419-4222-4bb2-a8b7-e036df090dfd>/linux-3.2.11
[2012-04-20 03:39:25.299732] W [client3_1-fops.c:2610:client3_1_lookup_cbk] 0-nfs-test-big-client-0: remote operation failed: Stale NFS file handle. Path: <gfid:fed32419-4222-4bb2-a8b7-e036df090dfd>/linux-3.2.11
[2012-04-20 03:39:25.299745] W [nfs3.c:1198:nfs3svc_lookup_cbk] 0-nfs: 2ef49f73: <gfid:fed32419-4222-4bb2-a8b7-e036df090dfd>/linux-3.2.11 => -1 (Stale NFS file handle)








Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2012-05-08 11:06:45 UTC
CHANGE: http://review.gluster.com/3274 (protocol/{client,server} : Log improvements) merged in master by Vijay Bellur (vijay@gluster.com)

Comment 2 Kaushal 2012-05-08 11:12:44 UTC
The above change doesn't actually solve this. Had put in the wrong bug-id for review. The change solves https://bugzilla.redhat.com/show_bug.cgi?id=812199 and https://bugzilla.redhat.com/show_bug.cgi?id=809713.

Comment 3 Amar Tumballi 2012-05-10 06:10:45 UTC
Sac,

The path printed in the log, is actually directly accessible in the backend, and also, with the current design it is very hard to print the exact path itself (as there will be no path passed in the fops).

Hence not planing to work on this bug. This will be properly documented to help GSS and users to understand which file is the one in backend.


for "<gfid:fed32419-4222-4bb2-a8b7-e036df090dfd>/linux-3.2.11" backend path will be "$export-path/.glusterfs/fd/d3/fed32419-4222-4bb2-a8b7-e036df090dfd/linux-3.2.11"

So taking it off the 3.3.0beta blocker state.

Comment 4 Sachidananda Urs 2012-05-21 07:40:11 UTC
(In reply to comment #3)
> Sac,
> 
> The path printed in the log, is actually directly accessible in the backend,
> and also, with the current design it is very hard to print the exact path
> itself (as there will be no path passed in the fops).
> 
> Hence not planing to work on this bug. This will be properly documented to
> help GSS and users to understand which file is the one in backend.
> 
> 
> for "<gfid:fed32419-4222-4bb2-a8b7-e036df090dfd>/linux-3.2.11" backend path
> will be
> "$export-path/.glusterfs/fd/d3/fed32419-4222-4bb2-a8b7-e036df090dfd/linux-3.
> 2.11"
> 
> So taking it off the 3.3.0beta blocker state.

Yes, makes sense.

Comment 5 Niels de Vos 2014-04-17 11:38:32 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.5.0, please reopen this bug report.

glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [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/6137
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


Note You need to log in before you can comment on or make changes to this bug.