Re: [Gluster-users] Geo replication stuck (rsync: link_stat "(unreachable)")

2017-04-12 Thread Kotresh Hiremath Ravishankar
Hi, I think the directory Workhours_2017 is deleted on master and on slave it's failing to delete because there might be stale linkto files at the back end. These issues are fixed in DHT with latest versions. Upgrading to latest version would solve these issues. To workaround the issue, you

Re: [Gluster-users] [Gluster-devel] Glusterfs meta data space consumption issue

2017-04-12 Thread Pranith Kumar Karampuri
Yes On Thu, Apr 13, 2017 at 8:21 AM, ABHISHEK PALIWAL wrote: > Means the fs where this brick has been created? > On Apr 13, 2017 8:19 AM, "Pranith Kumar Karampuri" > wrote: > >> Is your backend filesystem ext4? >> >> On Thu, Apr 13, 2017 at 6:29

Re: [Gluster-users] [Gluster-devel] Glusterfs meta data space consumption issue

2017-04-12 Thread ABHISHEK PALIWAL
Means the fs where this brick has been created? On Apr 13, 2017 8:19 AM, "Pranith Kumar Karampuri" wrote: > Is your backend filesystem ext4? > > On Thu, Apr 13, 2017 at 6:29 AM, ABHISHEK PALIWAL > wrote: > >> No,we are not using sharding >> On Apr

Re: [Gluster-users] [Gluster-devel] Glusterfs meta data space consumption issue

2017-04-12 Thread Pranith Kumar Karampuri
Is your backend filesystem ext4? On Thu, Apr 13, 2017 at 6:29 AM, ABHISHEK PALIWAL wrote: > No,we are not using sharding > On Apr 12, 2017 7:29 PM, "Alessandro Briosi" wrote: > >> Il 12/04/2017 14:16, ABHISHEK PALIWAL ha scritto: >> >> I have did more

Re: [Gluster-users] [Gluster-devel] Glusterfs meta data space consumption issue

2017-04-12 Thread ABHISHEK PALIWAL
No,we are not using sharding On Apr 12, 2017 7:29 PM, "Alessandro Briosi" wrote: > Il 12/04/2017 14:16, ABHISHEK PALIWAL ha scritto: > > I have did more investigation and find out that brick dir size is > equivalent to gluster mount point but .glusterfs having too much

Re: [Gluster-users] Geo replication stuck (rsync: link_stat "(unreachable)")

2017-04-12 Thread mabi
Hi Kotresh, Thanks for your hint, adding the "--ignore-missing-args" option to rsync and restarting geo-replication worked but it only managed to sync approximately 1/3 of the data until it put the geo replication in status "Failed" this time. Now I have a different type of error as you can

Re: [Gluster-users] [Gluster-devel] Glusterfs meta data space consumption issue

2017-04-12 Thread Alessandro Briosi
Il 12/04/2017 14:16, ABHISHEK PALIWAL ha scritto: > I have did more investigation and find out that brick dir size is > equivalent to gluster mount point but .glusterfs having too much > difference > You are probably using sharding? Buon lavoro. /Alessandro Briosi/ *METAL.it Nord S.r.l.* Via

Re: [Gluster-users] [Gluster-devel] Glusterfs meta data space consumption issue

2017-04-12 Thread ABHISHEK PALIWAL
I have did more investigation and find out that brick dir size is equivalent to gluster mount point but .glusterfs having too much difference opt/lvmdir/c2/brick # du -sch * 96K RNC_Exceptions 36K configuration 63Mjava 176K