Description of problem: While Iozone -a command is running in windows client, I am observing frequent warning messages are being logged in samba-client logs. No functional impact is seen as of now. frequency is almost 15 entries in 2 minutes. Version-Release number of selected component (if applicable): glusterfs-6.0-17.el7rhgs.x86_64 samba-4.9.8-109.el7rhgs.x86_64 Windows-10 How reproducible: Always Steps to Reproduce: 1. On a smb share mount on windows client 2. Execute iozone -a in the share 3. check the client log Actual results: Warning messages are seen Expected results: Concerned warning messages should not occur Additional info: (Not a Regression able to see this 105 build) [2019-10-14 17:56:24.720062] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-5: remote operation failed. Path: /Bench/iozone.tmp (dd128615-056f-4efa-b590-e99fce154926). Key: (null) [Permission denied] [2019-10-14 18:00:30.027220] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-1: remote operation failed. Path: /Bench/iozone.tmp (faf71b9c-6c42-462a-8dd3-5bd7d5242e8a). Key: (null) [Permission denied] [2019-10-14 18:08:12.975208] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-1: remote operation failed. Path: /Bench/iozone.tmp (faf71b9c-6c42-462a-8dd3-5bd7d5242e8a). Key: (null) [Permission denied] [2019-10-14 18:12:19.463416] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-2: remote operation failed. Path: /Bench/iozone.tmp (0cb3dfeb-352b-4f4f-9cc2-8f348b595815). Key: (null) [Permission denied] [2019-10-14 18:20:06.401266] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-2: remote operation failed. Path: /Bench/iozone.tmp (0cb3dfeb-352b-4f4f-9cc2-8f348b595815). Key: (null) [Permission denied] [2019-10-14 18:24:15.442265] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-0: remote operation failed. Path: /Bench/iozone.tmp (83b262a4-17a7-41a7-b738-ec20b07d0db4). Key: (null) [Permission denied] [2019-10-14 18:32:10.062038] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-0: remote operation failed. Path: /Bench/iozone.tmp (83b262a4-17a7-41a7-b738-ec20b07d0db4). Key: (null) [Permission denied] [2019-10-14 18:36:06.959691] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-4: remote operation failed. Path: /Bench/iozone.tmp (52164c5d-ba67-44fd-8a97-6e01e1c62ee6). Key: (null) [Permission denied] [2019-10-14 18:44:17.300383] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-4: remote operation failed. Path: /Bench/iozone.tmp (52164c5d-ba67-44fd-8a97-6e01e1c62ee6). Key: (null) [Permission denied] [2019-10-14 18:48:29.574751] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-1: remote operation failed. Path: /Bench/iozone.tmp (5e7f661f-df3b-4020-8d6e-36fe1dd93873). Key: (null) [Permission denied] [2019-10-14 18:56:49.030756] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-1: remote operation failed. Path: /Bench/iozone.tmp (5e7f661f-df3b-4020-8d6e-36fe1dd93873). Key: (null) [Permission denied] [2019-10-14 19:00:43.845504] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-1: remote operation failed. Path: /Bench/iozone.tmp (34b086d8-dc01-416d-b3f2-3664dae53645). Key: (null) [Permission denied] [2019-10-14 19:08:30.284944] W [MSGID: 114031] [client-rpc-fops_v2.c:921:client4_0_getxattr_cbk] 0-volkswagen-client-1: remote operation failed. Path: /Bench/iozone.tmp (34b086d8-dc01-416d-b3f2-3664dae53645). Key: (null) [Permission denied] Volume Name: volkswagen Type: Distributed-Disperse Volume ID: 1f050515-3726-49a8-be16-649894dd5a12 Status: Started Snapshot Count: 0 Number of Bricks: 2 x (4 + 2) = 12 Transport-type: tcp Bricks: Brick1: 10.70.43.54:/bricks/brick0/brick Brick2: 10.70.43.58:/bricks/brick0/brick Brick3: 10.70.43.141:/bricks/brick0/brick Brick4: 10.70.43.17:/bricks/brick0/brick Brick5: 10.70.43.115:/bricks/brick0/brick Brick6: 10.70.43.138:/bricks/brick0/brick Brick7: 10.70.43.54:/bricks/brick1/brick Brick8: 10.70.43.58:/bricks/brick1/brick Brick9: 10.70.43.141:/bricks/brick1/brick Brick10: 10.70.43.17:/bricks/brick1/brick Brick11: 10.70.43.115:/bricks/brick1/brick Brick12: 10.70.43.138:/bricks/brick1/brick Options Reconfigured: storage.batch-fsync-delay-usec: 0 server.allow-insecure: on transport.address-family: inet nfs.disable: on features.cache-invalidation: on features.cache-invalidation-timeout: 600 performance.cache-samba-metadata: on performance.stat-prefetch: on performance.cache-invalidation: on performance.md-cache-timeout: 600 network.inode-lru-limit: 200000 performance.nl-cache: on performance.nl-cache-timeout: 600 performance.readdir-ahead: on performance.parallel-readdir: on user.cifs: enable
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (samba bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4403