Bug 814666
| Summary: | client3_1-fops.c: Log enhancements | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Sachidananda Urs <sac> |
| Component: | protocol | Assignee: | GlusterFS Bugs list <gluster-bugs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | pre-release | CC: | gluster-bugs, rwheeler |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.5.0 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-04-17 11:38:32 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
Sachidananda Urs
2012-04-20 11:13:14 UTC
CHANGE: http://review.gluster.com/3274 (protocol/{client,server} : Log improvements) merged in master by Vijay Bellur (vijay) 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. 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. (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. 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 |