search for: sanoj

...can I do to fix that issue with the quotas? > -------- Original Message -------- > Subject: Re: [Gluster-users] Quotas not working after adding arbiter brick to replica 2 > Local Time: August 2, 2017 2:35 PM > UTC Time: August 2, 2017 12:35 PM > From: mabi at protonmail.ch > To: Sanoj Unnikrishnan <sunnikri at redhat.com> > Gluster Users <gluster-users at gluster.org> > Hi Sanoj, > I copied over the quota.conf file from the affected volume (node 1) and opened it up with a hex editor but can not recognize anything really except for the first few header/versio...

Thank you very much Sanoj, I ran your script once and it worked. I now have quotas again... Question: do you know in which release this issue will be fixed? > -------- Original Message -------- > Subject: Re: [Gluster-users] Quotas not working after adding arbiter brick to replica 2 > Local Time: August 4, 2017 3:...

Thanks for the swift turn around. Will try this out and let you know. Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkarampu at redhat.com] Sent: Monday, July 10, 2017 8:31 AM To: Sanoj Unnikrishnan Cc: Ankireddypalle Reddy; Gluster Devel (gluster-devel at gluster.org); gluster-users at gluster.org Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost Ram, If you see it again, you can use this. I am going to send out a patch for the code path which can le...

...to fix that issue with the quotas? > > -------- Original Message -------- > Subject: Re: [Gluster-users] Quotas not working after adding arbiter brick > to replica 2 > Local Time: August 2, 2017 2:35 PM > UTC Time: August 2, 2017 12:35 PM > From: mabi at protonmail.ch > To: Sanoj Unnikrishnan <sunnikri at redhat.com> > Gluster Users <gluster-users at gluster.org> > > Hi Sanoj, > > I copied over the quota.conf file from the affected volume (node 1) and > opened it up with a hex editor but can not recognize anything really except > for the fir...

...dy <areddy at commvault.com> wrote: > Thanks for the swift turn around. Will try this out and let you know. > > > > Thanks and Regards, > > Ram > > *From:* Pranith Kumar Karampuri [mailto:pkarampu at redhat.com] > *Sent:* Monday, July 10, 2017 8:31 AM > *To:* Sanoj Unnikrishnan > *Cc:* Ankireddypalle Reddy; Gluster Devel (gluster-devel at gluster.org); > gluster-users at gluster.org > > *Subject:* Re: [Gluster-devel] gfid and volume-id extended attributes lost > > > > Ram, > > If you see it again, you can use this. I am goi...

Mabi, We have fixed a couple of issues in the quota list path. Could you also please attach the quota.conf file (/var/lib/glusterd/vols/ patchy/quota.conf) (Ideally, the first few bytes would be ascii characters followed by 17 bytes per directory on which quota limit is set) Regards, Sanoj On Tue, Aug 1, 2017 at 1:36 PM, mabi <mabi at protonmail.ch> wrote: > I also just noticed quite a few of the following warning messages in the > quotad.log log file: > > [2017-08-01 07:59:27.834202] W [MSGID: 108027] [afr-common.c:2496:afr_discover_done] > 0-myvolume-replica...

Hi Sanoj, I copied over the quota.conf file from the affected volume (node 1) and opened it up with a hex editor but can not recognize anything really except for the first few header/version bytes. I have attached it within this mail (compressed with bzip2) as requested. Should I recreate them manually? the...

Ram, If you see it again, you can use this. I am going to send out a patch for the code path which can lead to removal of gfid/volume-id tomorrow. On Mon, 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 ch...

...5033):->posix_setxattr pid-966: 57 glusterfsd(5033):<-posix_setxattr pid-1423: 0 glusterfs(1431):->client_setxattr pid-1423: 37 glusterfs(1431):<-client_setxattr pid-1423: 0 glusterfs(1431):->client_setxattr pid-1423: 41 glusterfs(1431):<-client_setxattr Regards, Sanoj On Mon, Jul 10, 2017 at 2:56 PM, Sanoj Unnikrishnan <sunnikri at redhat.com> wrote: > @ 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 bac...

...ing SWAT.I'm not able to access the COMMIT CHANGES tab in swat which should be close to RESET VALUES and ADVANCED VIEW,to add further i dont even see the COMMIT CHNAGES tab on the screen anywhere,how am i supposed configure samba using swat.I would accept any recommendations.Pls do email me at sanoj200@hotmail.com regarding your troubleshooting suggestions. Thanks, Sincerely Sanoj George -------------- next part -------------- HTML attachment scrubbed and removed

...7 at 7:06 AM, Pranith Kumar Karampuri <pkarampu at redhat.com > wrote: > Ram, > As per the code, self-heal was the only candidate which *can* do > it. Could you check logs of self-heal daemon and the mount to check if > there are any metadata heals on root? > > > +Sanoj > > Sanoj, > Is there any systemtap script we can use to detect which process is > removing these xattrs? > > On Sat, Jul 8, 2017 at 2:58 AM, Ankireddypalle Reddy <areddy at commvault.com > > wrote: > >> We lost the attributes on all the bricks on servers...

Ram, As per the code, self-heal was the only candidate which *can* do it. Could you check logs of self-heal daemon and the mount to check if there are any metadata heals on root? +Sanoj Sanoj, Is there any systemtap script we can use to detect which process is removing these xattrs? On Sat, Jul 8, 2017 at 2:58 AM, Ankireddypalle Reddy <areddy at commvault.com> wrote: > We lost the attributes on all the bricks on servers glusterfs2 and > glusterfs3 again. >...

Dear Linux guru's Does Redhat version 7.3 support SWAT configuration coz i dont see the SWAT file under /etc/xinetd.d. Pls explain y Sincerely, Sanoj George -------------- next part -------------- HTML attachment scrubbed and removed

I cannot seem to get the options for usrquota to work with the mount, assuming this isn?t supported? I can set volume level quota however, our GlusterFS is backing servers with user accounts that require quota restrictions. It seems like if those users are placed on the mount that uses GlusterFS, they have no restrictions on storage. Any solution for this? Currently using the native gluster

I also just noticed quite a few of the following warning messages in the quotad.log log file: [2017-08-01 07:59:27.834202] W [MSGID: 108027] [afr-common.c:2496:afr_discover_done] 0-myvolume-replicate-0: no read subvols for (null) > -------- Original Message -------- > Subject: [Gluster-users] Quotas not working after adding arbiter brick to replica 2 > Local Time: August 1, 2017 8:49 AM

Hello, As you might have read in my previous post on the mailing list I have added an arbiter node to my GlusterFS 3.8.11 replica 2 volume. After some healing issues and help of Ravi that could get fixed but now I just noticed that my quotas are all gone. When I run the following command: glusterfs volume quota myvolume list There is no output... In the /var/log/glusterfs/quotad.log I can see the

We lost the attributes on all the bricks on servers glusterfs2 and glusterfs3 again. [root at glusterfs2 Log_Files]# gluster volume info Volume Name: StoragePool Type: Distributed-Disperse Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f Status: Started Number of Bricks: 20 x (2 + 1) = 60 Transport-type: tcp Bricks: Brick1: glusterfs1sds:/ws/disk1/ws_brick Brick2: glusterfs2sds:/ws/disk1/ws_brick

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

...ck this. Try quota list command with a specific limit mentioned in the command. gluster volume quota <VOLNAME> list <PATH> Make sure this path and the limit are set. If this works then you need to clean up the last stale entry. If this doesn't work we need to look further. Thanks Sanoj for the guidance. On Wed, Feb 14, 2018 at 1:36 AM, mabi <mabi at protonmail.ch> wrote: > I tried to set the limits as you suggest by running the following command. > > $ sudo gluster volume quota myvolume limit-usage /directory 200GB > volume quota : success > > but then wh...

...; >> gluster volume quota <VOLNAME> list <PATH> >> >> Make sure this path and the limit are set. >> >> If this works then you need to clean up the last stale entry. >> >> If this doesn't work we need to look further. >> >> Thanks Sanoj for the guidance. >> >> On Wed, Feb 14, 2018 at 1:36 AM, mabi mabi at protonmail.ch wrote: >> >> > I tried to set the limits as you suggest by running the following command. >> > >> > $ sudo gluster volume quota myvolume limit-usage /directory 200GB >...