search for: removexattr

...ver-rpc-fops.c:1317:server_ftruncate_cbk] > 0-c_glusterfs-server: 70: FTRUNCATE 0 (8f9c8054-b0d7-4b93-a95b-cd3ab249c56d)==> > (No space left on device) [No space left on device] > [2017-12-01 14:10:16.968515] E [MSGID: 113001] [posix.c:4616:_posix_remove_xattr] > 0-c_glusterfs-posix: removexattr failed on /opt/lvmdir/c2/brick/. > glusterfs/00/00/00000000-0000-0000-0000-000000000001/configuration (for > trusted.glusterfs.dht) [No space left on device] > [2017-12-01 14:10:16.968589] I [MSGID: 115058] > [server-rpc-fops.c:740:server_removexattr_cbk] 0-c_glusterfs-server: 90: >...

...at 5:19 PM, Sanoj Unnikrishnan <sunnikri at redhat.com<mailto:sunnikri at redhat.com>> wrote: Please use the systemtap script(https://paste.fedoraproject.org/paste/EGDa0ErwX0LV3y-gBYpfNA) to check which process is invoking remove xattr calls. It prints the pid, tid and arguments of all removexattr calls. I have checked for these fops at the protocol/client and posix translators. To run the script .. 1) install systemtap and dependencies. 2) install glusterfs-debuginfo 3) change the path of the translator in the systemtap script to appropriate values for your system (change "/usr/lib64/...

Ram, I sent https://review.gluster.org/17765 to fix the possibility in bulk removexattr. But I am not sure if this is indeed the reason for this issue. On Mon, Jul 10, 2017 at 6:30 PM, Ankireddypalle Reddy <areddy at commvault.com> wrote: > Thanks for the swift turn around. Will try this out and let you know. > > > > Thanks and Regards, > > Ram > > *...

Please use the systemtap script( https://paste.fedoraproject.org/paste/EGDa0ErwX0LV3y-gBYpfNA) to check which process is invoking remove xattr calls. It prints the pid, tid and arguments of all removexattr calls. I have checked for these fops at the protocol/client and posix translators. To run the script .. 1) install systemtap and dependencies. 2) install glusterfs-debuginfo 3) change the path of the translator in the systemtap script to appropriate values for your system (change "/usr/lib64/...

@ pranith , yes . we can get the pid on all removexattr call and also print the backtrace of the glusterfsd process when trigerring removing xattr. I will write the script and reply back. On Sat, Jul 8, 2017 at 7:06 AM, Pranith Kumar Karampuri <pkarampu at redhat.com > wrote: > Ram, > As per the code, self-heal was the only candidat...

...n, Jul 10, 2017 at 5:19 PM, Sanoj Unnikrishnan <sunnikri at redhat.com> wrote: > Please use the systemtap script(https://paste.fedoraproject.org/paste/ > EGDa0ErwX0LV3y-gBYpfNA) to check which process is invoking remove xattr > calls. > It prints the pid, tid and arguments of all removexattr calls. > I have checked for these fops at the protocol/client and posix translators. > > To run the script .. > 1) install systemtap and dependencies. > 2) install glusterfs-debuginfo > 3) change the path of the translator in the systemtap script to > appropriate values for you...

...at gluster.org > *Subject:* Re: [Gluster-devel] gfid and volume-id extended attributes lost > > > > > > > > On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com> > wrote: > > 3.7.19 > > > > These are the only callers for removexattr and only _posix_remove_xattr > has the potential to do removexattr as posix_removexattr already makes sure > that it is not gfid/volume-id. And surprise surprise _posix_remove_xattr > happens only from healing code of afr/ec. And this can only happen if the > source brick doesn't ha...

On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com> wrote: > 3.7.19 > These are the only callers for removexattr and only _posix_remove_xattr has the potential to do removexattr as posix_removexattr already makes sure that it is not gfid/volume-id. And surprise surprise _posix_remove_xattr happens only from healing code of afr/ec. And this can only happen if the source brick doesn't have gfid, which doesn...

...317:server_ftruncate_cbk] 0-c_glusterfs-server: 70: >> FTRUNCATE 0 (8f9c8054-b0d7-4b93-a95b-cd3ab249c56d)==> (No space left on >> device) [No space left on device] >> [2017-12-01 14:10:16.968515] E [MSGID: 113001] >> [posix.c:4616:_posix_remove_xattr] 0-c_glusterfs-posix: removexattr >> failed on /opt/lvmdir/c2/brick/.glusterfs/00/00/00000000-0000-0000- >> 0000-000000000001/configuration (for trusted.glusterfs.dht) [No space >> left on device] >> [2017-12-01 14:10:16.968589] I [MSGID: 115058] >> [server-rpc-fops.c:740:server_removexattr_cbk] 0-c_gl...

...palle 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 > > > > Did anything special happen on these two bricks? It can't happen in the > I/O path: > posix_removexattr() has: > 0 if (!strcmp (GFID_XATTR_KEY, name)) > { > > > 1 gf_msg (this->name, GF_LOG_WARNING, 0, > P_MSG_XATTR_NOT_REMOVED, > 2 "Remove xattr called on gfid for file %s", > real_path); > 3...

...l at gluster.org<mailto:gluster-devel at gluster.org>); gluster-users at gluster.org<mailto:gluster-users at gluster.org> Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost Did anything special happen on these two bricks? It can't happen in the I/O path: posix_removexattr() has: 0 if (!strcmp (GFID_XATTR_KEY, name)) { 1 gf_msg (this->name, GF_LOG_WARNING, 0, P_MSG_XATTR_NOT_REMOVED, 2 "Remove xattr called on gfid for file %s", real_path); 3 op_ret = -1; 4 goto out;...

...er-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:25 PM, Ankireddypalle Reddy <areddy at commvault.com<mailto:areddy at commvault.com>> wrote: 3.7.19 These are the only callers for removexattr and only _posix_remove_xattr has the potential to do removexattr as posix_removexattr already makes sure that it is not gfid/volume-id. And surprise surprise _posix_remove_xattr happens only from healing code of afr/ec. And this can only happen if the source brick doesn't have gfid, which doesn...

Did anything special happen on these two bricks? It can't happen in the I/O path: posix_removexattr() has: 0 if (!strcmp (GFID_XATTR_KEY, name)) { 1 gf_msg (this->name, GF_LOG_WARNING, 0, P_MSG_XATTR_NOT_REMOVED, 2 "Remove xattr called on gfid for file %s", real_path); 3 op_ret = -1; 4 goto out...

...cate_cbk] 0-c_glusterfs-server: 70: >>> FTRUNCATE 0 (8f9c8054-b0d7-4b93-a95b-cd3ab249c56d)==> (No space left on >>> device) [No space left on device] >>> [2017-12-01 14:10:16.968515] E [MSGID: 113001] >>> [posix.c:4616:_posix_remove_xattr] 0-c_glusterfs-posix: removexattr >>> failed on /opt/lvmdir/c2/brick/.glusterfs/00/00/00000000-0000-0000-0000-000000000001/configuration >>> (for trusted.glusterfs.dht) [No space left on device] >>> [2017-12-01 14:10:16.968589] I [MSGID: 115058] >>> [server-rpc-fops.c:740:server_removexattr_cbk]...

...us 0.00 us 1035 > RELEASEDIR > 0.00 827.00 us 619.00 us 1199.00 us 10 > READDIRP > 0.00 98.38 us 30.00 us 535.00 us 144 > ENTRYLK > 0.00 180.11 us 121.00 us 257.00 us 94 > REMOVEXATTR > 0.00 208.03 us 23.00 us 1980.00 us 182 > GETXATTR > 0.00 1212.71 us 35.00 us 29459.00 us 38 > READDIR > 0.01 260.39 us 172.00 us 552.00 us 376 > XATTROP > 0.01 305.10 us 45....

...usterfs-server: >>>> 70: FTRUNCATE 0 (8f9c8054-b0d7-4b93-a95b-cd3ab249c56d)==> (No space >>>> left on device) [No space left on device] >>>> [2017-12-01 14:10:16.968515] E [MSGID: 113001] >>>> [posix.c:4616:_posix_remove_xattr] 0-c_glusterfs-posix: removexattr >>>> failed on /opt/lvmdir/c2/brick/.glusterfs/00/00/00000000-0000-0000-0000-000000000001/configuration >>>> (for trusted.glusterfs.dht) [No space left on device] >>>> [2017-12-01 14:10:16.968589] I [MSGID: 115058] >>>> [server-rpc-fops.c:740:server_r...

...035 >> RELEASEDIR >> 0.00 827.00 us 619.00 us 1199.00 us 10 >> READDIRP >> 0.00 98.38 us 30.00 us 535.00 us 144 >> ENTRYLK >> 0.00 180.11 us 121.00 us 257.00 us 94 >> REMOVEXATTR >> 0.00 208.03 us 23.00 us 1980.00 us 182 >> GETXATTR >> 0.00 1212.71 us 35.00 us 29459.00 us 38 >> READDIR >> 0.01 260.39 us 172.00 us 552.00 us 376 >> XATTROP >>...

...@@ -55,6 +55,7 @@ static guestfs_int_xattr_list *getxattrs (const char *path, ssize_t (*listxattr) static int _setxattr (const char *xattr, const char *val, int vallen, const char *path, int (*setxattr) (const char *path, const char *name, const void *value, size_t size, int flags)); static int _removexattr (const char *xattr, const char *path, int (*removexattr) (const char *path, const char *name)); static char *_listxattrs (const char *path, ssize_t (*listxattr) (const char *path, char *list, size_t size), ssize_t *size); +static char *_getxattr (const char *name, const char *path, ssize_t (*getxa...

...>>> 0.00 827.00 us 619.00 us 1199.00 us 10 >>> READDIRP >>> 0.00 98.38 us 30.00 us 535.00 us 144 >>> ENTRYLK >>> 0.00 180.11 us 121.00 us 257.00 us 94 >>> REMOVEXATTR >>> 0.00 208.03 us 23.00 us 1980.00 us 182 >>> GETXATTR >>> 0.00 1212.71 us 35.00 us 29459.00 us 38 >>> READDIR >>> 0.01 260.39 us 172.00 us 552.00 us 376 >>>...

...txattr failed on /export/brick1/: user.DOSATTRIB (No data available) another error: [2013-05-10 15:49:54.998621] E [posix.c:2583:posix_getxattr] 0-dfsvol01-posix: getxattr failed on /export/brick1/: system.posix_acl_access (No data available) [2013-05-10 15:49:55.028892] E [marker.c:2136:marker_removexattr_cbk] 0-dfsvol01-marker: No data available occurred while creating symlinks [2013-05-10 15:49:55.028952] I [server3_1-fops.c:738:server_removexattr_cbk] 0-dfsvol01-server: 127: REMOVEXATTR / (00000000-0000-0000-0000-000000000001) ==> -1 (No data available) And it's right, there is no da...