Re: [Gluster-devel] gfid and volume-id extended attributes lost

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

Re: [Gluster-devel] gfid and volume-id extended attributes lost

@ 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 wrote: > Ram, >As per

Re: [Gluster-devel] gfid and volume-id extended attributes lost

Thanks for the swift turn around. Will try this out and let you know. Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkara...@redhat.com] Sent: Monday, July 10, 2017 8:31 AM To: Sanoj Unnikrishnan Cc: Ankireddypalle Reddy; Gluster Devel (gluster-devel@gluster.org);

[Gluster-devel] A few network change, maybe a jenkins restart

Hi, I am trying to reduce our usage of ipv4 (among others), so I may start to move a few VM around. I am gonna start by the freebsd10.3 in the cage, move it to the internal network. This might requires me to restart it, and might imply some restart of jenkins (for changing network configuration