search for: sys_fremovexattr

...ttr' lib/system.c: In function 'sys_flistxattr': lib/system.c:1741: error: too few arguments to function 'flistxattr' lib/system.c: In function 'sys_removexattr': lib/system.c:1759: error: too few arguments to function 'removexattr' lib/system.c: In function 'sys_fremovexattr': lib/system.c:1811: error: too few arguments to function 'fremovexattr' lib/system.c: In function 'sys_setxattr': lib/system.c:1842: error: too few arguments to function 'setxattr' lib/system.c: In function 'sys_fsetxattr': lib/system.c:1939: error: too few argu...

...lt;init>> sys_lremovexattr (dir_data->data, "trusted.glusterfs.test"); So there are only two possibilities: 1) Source directory in ec/afr doesn't have gfid 2) Something else removed these xattrs. What is your volume info? May be that will give more clues. PS: sys_fremovexattr is called only from posix_fremovexattr(), so that doesn't seem to be the culprit as it also have checks to guard against gfid/volume-id removal. > > Thanks and Regards, > > Ram > > *From:* Pranith Kumar Karampuri [mailto:pkarampu at redhat.com] > *Sent:* Friday, July 07,...

...;<init>> sys_lremovexattr (dir_data->data, "trusted.glusterfs.test"); So there are only two possibilities: 1) Source directory in ec/afr doesn't have gfid 2) Something else removed these xattrs. What is your volume info? May be that will give more clues. PS: sys_fremovexattr is called only from posix_fremovexattr(), so that doesn't seem to be the culprit as it also have checks to guard against gfid/volume-id removal. Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkarampu at redhat.com<mailto:pkarampu at redhat.com>] Sent: Friday, July 07, 201...

...gt;data, "trusted.glusterfs.test"); > > So there are only two possibilities: > > 1) Source directory in ec/afr doesn't have gfid > > 2) Something else removed these xattrs. > > What is your volume info? May be that will give more clues. > > > > PS: sys_fremovexattr is called only from posix_fremovexattr(), so that > doesn't seem to be the culprit as it also have checks to guard against > gfid/volume-id removal. > > > > Thanks and Regards, > > Ram > > *From:* Pranith Kumar Karampuri [mailto:pkarampu at redhat.com] > *Sent:*...

...t;> >> So there are only two possibilities: >> >> 1) Source directory in ec/afr doesn't have gfid >> >> 2) Something else removed these xattrs. >> >> What is your volume info? May be that will give more clues. >> >> >> >> PS: sys_fremovexattr is called only from posix_fremovexattr(), so that >> doesn't seem to be the culprit as it also have checks to guard against >> gfid/volume-id removal. >> >> >> >> Thanks and Regards, >> >> Ram >> >> *From:* Pranith Kumar Karampuri [mai...

...ssibilities: >>> >>> 1) Source directory in ec/afr doesn't have gfid >>> >>> 2) Something else removed these xattrs. >>> >>> What is your volume info? May be that will give more clues. >>> >>> >>> >>> PS: sys_fremovexattr is called only from posix_fremovexattr(), so that >>> doesn't seem to be the culprit as it also have checks to guard against >>> gfid/volume-id removal. >>> >>> >>> >>> Thanks and Regards, >>> >>> Ram >>> >>&...

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

...t;> 1) Source directory in ec/afr doesn't have gfid >>>> >>>> 2) Something else removed these xattrs. >>>> >>>> What is your volume info? May be that will give more clues. >>>> >>>> >>>> >>>> PS: sys_fremovexattr is called only from posix_fremovexattr(), so that >>>> doesn't seem to be the culprit as it also have checks to guard against >>>> gfid/volume-id removal. >>>> >>>> >>>> >>>> Thanks and Regards, >>>> >>&gt...

...;<init>> sys_lremovexattr (dir_data->data, "trusted.glusterfs.test"); So there are only two possibilities: 1) Source directory in ec/afr doesn't have gfid 2) Something else removed these xattrs. What is your volume info? May be that will give more clues. PS: sys_fremovexattr is called only from posix_fremovexattr(), so that doesn't seem to be the culprit as it also have checks to guard against gfid/volume-id removal. Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkarampu at redhat.com<mailto:pkarampu at redhat.com>] Sent: Friday, July 07, 201...

...gt;data, "trusted.glusterfs.test"); > > So there are only two possibilities: > > 1) Source directory in ec/afr doesn't have gfid > > 2) Something else removed these xattrs. > > What is your volume info? May be that will give more clues. > > > > PS: sys_fremovexattr is called only from posix_fremovexattr(), so that > doesn't seem to be the culprit as it also have checks to guard against > gfid/volume-id removal. > > > > Thanks and Regards, > > Ram > > *From:* Pranith Kumar Karampuri [mailto:pkarampu at redhat.com] > *Sent:*...

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