Description of problem: *********************************** When any file operation(create,open,write,delete) is done on the root of volume(distributed) from smb mount point, In the brick log messages it is showing the following errors and logs the message which points that the lookup is happening for parent of root. snip from log: ************************************* [2014-02-11 11:49:14.251989] E [posix.c:3537:posix_fgetxattr] 0-dis-posix: fgetxattr failed on key system.posix_acl_access (No data available) [2014-02-11 11:49:14.252007] I [server-rpc-fops.c:869:server_fgetxattr_cbk] 0-dis-server: 11223: FGETXATTR 0 (9ba55abc-ed2a-4cfd-8451-9f052af4e506) (system.posix_acl_access) ==> (No data available) [2014-02-11 11:49:14.280511] E [posix.c:199:posix_lookup] 0-dis-posix: buf->ia_gfid is null for /rhs/brick1/dis/b1/.. [2014-02-11 11:49:14.280530] I [server-rpc-fops.c:149:server_lookup_cbk] 0-dis-server: 11269: LOOKUP /.. (00000000-0000-0000-0000-000000000001/..) ==> (No data available) [2014-02-11 11:49:19.068972] E [posix.c:199:posix_lookup] 0-dis-posix: buf->ia_gfid is null for /rhs/brick1/dis/b1/.. [2014-02-11 11:49:19.068994] I [server-rpc-fops.c:149:server_lookup_cbk] 0-dis-server: 11467: LOOKUP /.. (00000000-0000-0000-0000-000000000001/..) ==> (No data available) [2014-02-11 11:50:43.218278] E [posix.c:199:posix_lookup] 0-dis-posix: buf->ia_gfid is null for /rhs/brick1/dis/b1/.. [2014-02-11 11:50:43.218312] I [server-rpc-fops.c:149:server_lookup_cbk] 0-dis-server: 11653: LOOKUP /.. (00000000-0000-0000-0000-000000000001/..) ==> (No data available) [2014-02-11 11:50:43.287549] E [posix.c:199:posix_lookup] 0-dis-posix: buf->ia_gfid is null for /rhs/brick1/dis/b1/.. [2014-02-11 11:50:43.287568] I [server-rpc-fops.c:149:server_lookup_cbk] 0-dis-server: 11715: LOOKUP /.. (00000000-0000-0000-0000-000000000001/..) ==> (No data available) [2014-02-11 11:50:43.393521] E [posix.c:3537:posix_fgetxattr] 0-dis-posix: fgetxattr failed on key system.posix_acl_access (No data available) [2014-02-11 11:50:43.393540] I [server-rpc-fops.c:869:server_fgetxattr_cbk] 0-dis-server: 11820: FGETXATTR 7 (f1e7ed2b-35dc-4a83-922f-d34e4d5682ef) (system.posix_acl_access) ==> (No data available) [2014-02-11 11:50:43.468833] E [posix.c:199:posix_lookup] 0-dis-posix: buf->ia_gfid is null for /rhs/brick1/dis/b1/.. [2014-02-11 11:50:43.468852] I [server-rpc-fops.c:149:server_lookup_cbk] 0-dis-server: 11903: LOOKUP /.. (00000000-0000-0000-0000-000000000001/..) ==> (No data available) [2014-02-11 11:50:49.803079] E [posix.c:199:posix_lookup] 0-dis-posix: buf->ia_gfid is null for /rhs/brick1/dis/b1/.. [2014-02-11 11:50:49.803100] I [server-rpc-fops.c:149:server_lookup_cbk] 0-dis-server: 12052: LOOKUP /.. (00000000-0000-0000-0000-000000000001/..) ==> (No data availabl Version-Release number of selected component (if applicable): glusterfs-3.4.0.59rhs-1.el6rhs.x86_64 samba-glusterfs-3.6.9-167.10.el6rhs.x86_64 How reproducible: Log messages are seen for every file op. Steps to Reproduce: 1.Create a distributed volume. 2.Mount on windows client via smb. 3.Do file operations like create.open,write ,delete a file. 4.Check the brick logs: Actual results: In brick logs : following errors are seen:which points that the lookup is going for parent of root directory. [2014-02-11 11:50:43.218278] E [posix.c:199:posix_lookup] 0-dis-posix: buf->ia_gfid is null for /rhs/brick1/dis/b1/.. [2014-02-11 11:50:43.218312] I [server-rpc-fops.c:149:server_lookup_cbk] 0-dis-server: 11653: LOOKUP /.. (00000000-0000-0000-0000-000000000001/..) ==> (No data available) [2014-02-11 11:50:43.287549] E [posix.c:199:posix_lookup] 0-dis-posix: buf->ia_gfid is null for /rhs/brick1/dis/b1/.. [2014-02-11 11:50:43.287568] I [server-rpc-fops.c:149:server_lookup_cbk] 0-dis-server: 11715: LOOKUP /.. (00000000-0000-0000-0000-000000000001/..) ==> (No data available) [2014-02-11 11:50:43.393521] E [posix.c:3537:posix_fgetxattr] 0-dis-posix: fgetxattr failed on key system.posix_acl_access (No data available) Expected results: No such errors should be there. Additional info:
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/ If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.