[Bugs] [Bug 1379935] New: SMB[md-cache Private Build]: Error messages in brick logs related to upcall_cache_invalidate gf_uuid_is_null

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1379935

            Bug ID: 1379935
           Summary: SMB[md-cache Private Build]:Error messages in brick
                    logs related to upcall_cache_invalidate
                    gf_uuid_is_null
           Product: GlusterFS
           Version: 3.8
         Component: md-cache
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: sbhaloth at redhat.com
                CC: bugs at gluster.org



Description of problem:
*******************************

On running test cases related to AFR self heal on creating multiple files and
directories , there are log errors related to gf_uuid_is_null in
upcall_cache_invalidate.

The errors occurs where there is file create/write operation.

[2016-09-27 06:35:20.639063] E [upcall-internal.c:512:upcall_cache_invalidate]
(-->/usr/lib64/glusterfs/3.8.3/xlator/features/access-control.so(+0xad09)
[0x7fd90aca4d09]
-->/usr/lib64/glusterfs/3.8.3/xlator/features/locks.so(+0xd4f2)
[0x7fd90aa834f2]
-->/usr/lib64/glusterfs/3.8.3/xlator/features/upcall.so(+0x6cae)
[0x7fd90a238cae] ) 0-upcall_cache_invalidate: invalid argument:
!(gf_uuid_is_null (up_inode_ctx->gfid)) [Invalid argument]
[2016-09-27 06:35:22.717196] E [upcall-internal.c:512:upcall_cache_invalidate]
(-->/usr/lib64/glusterfs/3.8.3/xlator/features/access-control.so(+0xad09)
[0x7fd90aca4d09]
-->/usr/lib64/glusterfs/3.8.3/xlator/features/locks.so(+0xd4f2)
[0x7fd90aa834f2]
-->/usr/lib64/glusterfs/3.8.3/xlator/features/upcall.so(+0x6cae)
[0x7fd90a238cae] ) 0-upcall_cache_invalidate: invalid argument:
!(gf_uuid_is_null (up_inode_ctx->gfid)) [Invalid argument]
[2016-09-27 06:36:20.976194] E [upcall-internal.c:512:upcall_cache_invalidate]
(-->/usr/lib64/glusterfs/3.8.3/xlator/features/access-control.so(+0xad09)
[0x7fd90aca4d09]
-->/usr/lib64/glusterfs/3.8.3/xlator/features/locks.so(+0xd4f2)
[0x7fd90aa834f2]
-->/usr/lib64/glusterfs/3.8.3/xlator/features/upcall.so(+0x6cae)
[0x7fd90a238cae] ) 0-upcall_cache_invalidate: invalid argument:
!(gf_uuid_is_null (up_inode_ctx->gfid)) [Invalid argument]

Volume Name: vol1
Type: Distributed-Replicate
Volume ID: afb432f1-55d4-463c-bd50-ba19a63561e3
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.70.47.64:/mnt/brick/vol1/b1
Brick2: 10.70.47.66:/mnt/brick/vol1/b2
Brick3: 10.70.47.64:/mnt/brick/vol1/b3
Brick4: 10.70.47.66:/mnt/brick/vol1/b4
Options Reconfigured:
nfs.disable: on
performance.readdir-ahead: on
transport.address-family: inet
storage.batch-fsync-delay-usec: 0
server.allow-insecure: on
performance.stat-prefetch: on
features.cache-invalidation: on
features.cache-invalidation-timeout: 600
performance.cache-samba-metadata: on
performance.cache-invalidation: on
performance.md-cache-timeout: 600
cluster.metadata-self-heal: off
cluster.data-self-heal: off
cluster.entry-self-heal: off
cluster.self-heal-daemon: on
cluster.data-self-heal-algorithm: full



Version-Release number of selected component (if applicable):
glusterfs-3.8.3-0.39.git97d1dde.el7.x86_64


How reproducible:
Always 

Steps to Reproduce:
1. Create 2x2 volume, se vol options for md-cache , mount it on cifs
2. Start creating directories and files and run afr cases with brick down
3. observe logs for any errors

Actual results:
Lots of error messages related to upcall_cache_invalidate on create/write.


Expected results:
These type of error messages shouldn't be there.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.