search for: sys_lremovexattr

...fr/ec. And this can only happen if the source brick doesn't have gfid, which doesn't seem to match with the situation you explained. # line filename / context / line 1 1234 xlators/mgmt/glusterd/src/glusterd-quota.c <<glusterd_remove_quota_limit>> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_KEY); 2 1243 xlators/mgmt/glusterd/src/glusterd-quota.c <<glusterd_remove_quota_limit>> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_OBJECTS_KEY); 3 6102 xlators/mgmt/glusterd/src/glusterd-utils.c <<glusterd_check_and_set_brick_xattr&...

...fr/ec. And this can only happen if the source brick doesn't have gfid, which doesn't seem to match with the situation you explained. # line filename / context / line 1 1234 xlators/mgmt/glusterd/src/glusterd-quota.c <<glusterd_remove_quota_limit>> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_KEY); 2 1243 xlators/mgmt/glusterd/src/glusterd-quota.c <<glusterd_remove_quota_limit>> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_OBJECTS_KEY); 3 6102 xlators/mgmt/glusterd/src/glusterd-utils.c <<glusterd_check_and_set_brick_xattr&...

...the > source brick doesn't have gfid, which doesn't seem to match with the > situation you explained. > > # line filename / context / line > 1 1234 xlators/mgmt/glusterd/src/glusterd-quota.c > <<glusterd_remove_quota_limit>> > ret = sys_lremovexattr (abspath, QUOTA_LIMIT_KEY); > 2 1243 xlators/mgmt/glusterd/src/glusterd-quota.c > <<glusterd_remove_quota_limit>> > ret = sys_lremovexattr (abspath, QUOTA_LIMIT_OBJECTS_KEY); > 3 6102 xlators/mgmt/glusterd/src/glusterd-utils.c > <<glusterd_c...

...oesn't have gfid, which doesn't seem to match with the >> situation you explained. >> >> # line filename / context / line >> 1 1234 xlators/mgmt/glusterd/src/glusterd-quota.c >> <<glusterd_remove_quota_limit>> >> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_KEY); >> 2 1243 xlators/mgmt/glusterd/src/glusterd-quota.c >> <<glusterd_remove_quota_limit>> >> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_OBJECTS_KEY); >> 3 6102 xlators/mgmt/glusterd/src/glusterd-utils.c >&gt...

...ich doesn't seem to match with the >>> situation you explained. >>> >>> # line filename / context / line >>> 1 1234 xlators/mgmt/glusterd/src/glusterd-quota.c >>> <<glusterd_remove_quota_limit>> >>> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_KEY); >>> 2 1243 xlators/mgmt/glusterd/src/glusterd-quota.c >>> <<glusterd_remove_quota_limit>> >>> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_OBJECTS_KEY); >>> 3 6102 xlators/mgmt/glusterd/src/glusterd...

3.7.19 Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkarampu at redhat.com] Sent: Friday, July 07, 2017 11:54 AM To: Ankireddypalle Reddy Cc: Gluster Devel (gluster-devel at gluster.org); gluster-users at gluster.org Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost On Fri, Jul 7, 2017 at 9:20 PM, Ankireddypalle Reddy <areddy at

...match with the >>>> situation you explained. >>>> >>>> # line filename / context / line >>>> 1 1234 xlators/mgmt/glusterd/src/glusterd-quota.c >>>> <<glusterd_remove_quota_limit>> >>>> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_KEY); >>>> 2 1243 xlators/mgmt/glusterd/src/glusterd-quota.c >>>> <<glusterd_remove_quota_limit>> >>>> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_OBJECTS_KEY); >>>> 3 6102 xlators/mgmt/glust...

...fr/ec. And this can only happen if the source brick doesn't have gfid, which doesn't seem to match with the situation you explained. # line filename / context / line 1 1234 xlators/mgmt/glusterd/src/glusterd-quota.c <<glusterd_remove_quota_limit>> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_KEY); 2 1243 xlators/mgmt/glusterd/src/glusterd-quota.c <<glusterd_remove_quota_limit>> ret = sys_lremovexattr (abspath, QUOTA_LIMIT_OBJECTS_KEY); 3 6102 xlators/mgmt/glusterd/src/glusterd-utils.c <<glusterd_check_and_set_brick_xattr&...

...the > source brick doesn't have gfid, which doesn't seem to match with the > situation you explained. > > # line filename / context / line > 1 1234 xlators/mgmt/glusterd/src/glusterd-quota.c > <<glusterd_remove_quota_limit>> > ret = sys_lremovexattr (abspath, QUOTA_LIMIT_KEY); > 2 1243 xlators/mgmt/glusterd/src/glusterd-quota.c > <<glusterd_remove_quota_limit>> > ret = sys_lremovexattr (abspath, QUOTA_LIMIT_OBJECTS_KEY); > 3 6102 xlators/mgmt/glusterd/src/glusterd-utils.c > <<glusterd_c...

On Fri, Jul 7, 2017 at 9:20 PM, Ankireddypalle Reddy <areddy at commvault.com> wrote: > Pranith, > > Thanks for looking in to the issue. The bricks were > mounted after the reboot. One more thing that I noticed was when the > attributes were manually set when glusterd was up then on starting the > volume the attributes were again lost. Had to stop glusterd

https://bugzilla.samba.org/show_bug.cgi?id=6633 Summary: Extended attributes under Solaris are not supported. Product: rsync Version: 3.0.6 Platform: All OS/Version: Solaris Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: Lloyd.Parkes at

...' undeclared (first use in this function) lib/sysxattrs.c: In function `sys_lsetxattr': lib/sysxattrs.c:95: warning: implicit declaration of function `extattr_set_link' lib/sysxattrs.c:95: `EXTATTR_NAMESPACE_USER' undeclared (first use in this function) lib/sysxattrs.c: In function `sys_lremovexattr': lib/sysxattrs.c:100: warning: implicit declaration of function `extattr_delete_link' lib/sysxattrs.c:100: `EXTATTR_NAMESPACE_USER' undeclared (first use in this function) lib/sysxattrs.c: In function `sys_llistxattr': lib/sysxattrs.c:106: warning: implicit declaration of function...

...urn(-1); + } + + attrfd = attropen(path, name, AT_SYMLINK_NOFOLLOW|O_CREAT|O_RDWR,mode); + + if(attrfd>0) { + + for(bufpos=0;bufpos<size;) { + w = write(attrfd, value+bufpos, size); + if(w<0) return -errno; + bufpos+=w; + + } + close(attrfd); + return (bufpos); +} +return 0; +} + +int sys_lremovexattr(const char *path, const char *name) +{ + int attrdirfd; + int error; + STRUCT_STAT fst; + + do_lstat(path,&fst); + + if(S_ISLNK(fst.st_mode)) { + errno=EPERM; + return(-1); + } + + attrdirfd = attropen(path, ".", O_RDONLY); + + error = unlinkat(attrdirfd,name,0); + + close (attrdirf...

Hello group, I have an OSX 10.3.9 Server that I'm trying to back up with rsync 3.0.2. Since I didn't have any luck with the 10.3.9 patch and I do have 10.4 clients, I decided to try running the backup over AFP (Apple's file sharing protocol). I found a way to mount the AFP volume with root permissions and rsync 3.0.2 works very nicely using this on the 10.4 clients, preserving

This is a PoC patch for NFSv4/ZFS ACLs. The objective of the patch is that rsync --acls support NFSv4/ZFS ACLs without requiring a new command line option NFSv4 ACLs can't be represented using POSIX draft ACLs, if an NFSv4 ACL is present a separate POSIX draft ACL will not be present and there are new APIs to access NFSv4 ACLs. So we need to distinguish between NFSv4 ACLs and POSIX ACLs in