[Bugs] [Bug 1250441] New: Sharding - Excessive logging of messages of the kind 'Failed to get trusted.glusterfs.shard.file-size for bf292f5b-6dd6-45a8-b03c-aaf5bb973c50'

[bugzilla at redhat.com]

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

            Bug ID: 1250441
           Summary: Sharding - Excessive logging of messages of the kind
                    'Failed to get trusted.glusterfs.shard.file-size for
                    bf292f5b-6dd6-45a8-b03c-aaf5bb973c50'
           Product: GlusterFS
           Version: mainline
         Component: sharding
          Assignee: bugs at gluster.org
          Reporter: kdhananj at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



Description of problem:
On enabling features.shard on a volume which already has few files, performing
operations on the mount is causing excessive logging of messages of the
following kind:

[2015-08-05 10:57:48.743352] E [shard.c:232:shard_modify_size_and_block_count]
2-dis-shard: Failed to get trusted.glusterfs.shard.file-size for
0b2bd401-c438-4d57-8ae5-8d26105d3396

Turns out this is coming from readdir callback of shard translator where the
translator unconditionally looks for the xattr
'trusted.glusterfs.shard.file-size' in every entry's rsp dict and logs this
error on not finding it. But files that are not sharded (i.e., the ones that
were created before sharding was enabled on the volume) will not (and should
not!) have this xattr associated with them. So these logs are misleading and
must be suppressed in readdir(p).
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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