Bug 1534602 - FUSE reverse notificatons are not written to fuse dump
Summary: FUSE reverse notificatons are not written to fuse dump
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: fuse
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Csaba Henk
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-15 14:34 UTC by Csaba Henk
Modified: 2018-03-15 11:25 UTC (History)
2 users (show)

Fixed In Version: glusterfs-4.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-15 11:25:40 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Csaba Henk 2018-01-15 14:34:26 UTC
Description of problem:

With the --dump-fuse option, the glusterfs fuse client writes out fuse traffic to the given dump file. Reverese messages (aka. notifications) that are initiated by the glusterfs client (FUSE server) are not recorded in the dump.

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

All.

How reproducible:

Always.

Steps to Reproduce:
1. Mount a gluster volume with direct glusterfs invocation, using --dump-fuse:

# glusterfs --volfile-server=<host> --volfile-id=<vol> --dump-fuse=/path/to/dump.fuse ... <mountpoint>

2. On some file of the gluster mount, trigger an entry invalidation with

$ setfattr -n inode-invalidate -v whatever <file>

(the "whatever" can be whatever, just not an empty string!)

3. Compile parsefuse (https://github.com/csabahenk/parsefuse/, at this commit: https://github.com/csabahenk/parsefuse/commit/0232410 or later) for the glusterfs setup used, and feed it with the fuse dump and seek NOTIFY in the output:

$ sudo cat /path/to/dump.fuse | parsefuse | grep NOTIFY

Actual results:

Nada.

Expected results:

Entry shown with NOTIFY_INVAL_ENTRY label.

Additional info:

Comment 1 Worker Ant 2018-01-15 23:42:20 UTC
REVIEW: https://review.gluster.org/19196 (fuse: write out reverse notification to fuse dump) posted (#1) for review on master by Csaba Henk

Comment 2 Worker Ant 2018-01-17 00:01:08 UTC
COMMIT: https://review.gluster.org/19196 committed in master by \"Csaba Henk\" <csaba> with a commit message- fuse: write out reverse notification to fuse dump

BUG: 1534602
Change-Id: Ide42cf9cffe462d0cc46272b327c2a05999f09ba
Signed-off-by: Csaba Henk <csaba>

Comment 3 Shyamsundar 2018-03-15 11:25:40 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-4.0.0, please open a new bug report.

glusterfs-4.0.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://lists.gluster.org/pipermail/announce/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/


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