[Bugs] [Bug 1753561] New: Custom xattrs are not healed on newly added brick

bugzilla at redhat.com bugzilla at redhat.com
Thu Sep 19 09:57:36 UTC 2019


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

            Bug ID: 1753561
           Summary: Custom xattrs are not healed on newly added brick
           Product: GlusterFS
           Version: 6
            Status: NEW
         Component: distribute
          Keywords: Triaged
          Severity: medium
          Priority: medium
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: atumball at redhat.com, bugs at gluster.org,
                    moagrawa at redhat.com, rhs-bugs at redhat.com,
                    sankarshan at redhat.com, storage-qa-internal at redhat.com,
                    tdesala at redhat.com
        Depends On: 1702298, 1702299
  Target Milestone: ---
    Classification: Community



+++ This bug was initially created as a clone of Bug #1702299 +++

+++ This bug was initially created as a clone of Bug #1702298 +++

Description of problem:
Custom xattrs are not healed on newly added brick

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


How reproducible:
Always

Steps to Reproduce:
1.Setup 1x4 volume and mount the volume on /mnt
2.Create some directory mkdir /mnt/tmp{1..10}
3.Setup user.foo on all directories
  setfattr -n user.foo -v "abc" /mnt/tmp{1..10}
4. Added two new bricks
5. Run lookup on mount point
   ls -laR /mnt/    
6. Check xattr should heal for all directories on the backend on 
   newly added bricks

Actual results:

xattr are not healed on newly added brick
Expected results:
xattr should heal on newly added brick

Additional info:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1702298
[Bug 1702298] Custom xattrs are not healed on newly added brick
https://bugzilla.redhat.com/show_bug.cgi?id=1702299
[Bug 1702299] Custom xattrs are not healed on newly added brick
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list