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

There is no need but it could happen accidentally and I think it should be protect or should not be permissible. On Mon, Apr 17, 2017 at 8:36 AM, Atin Mukherjee wrote: > > > On Mon, 17 Apr 2017 at 08:23, ABHISHEK PALIWAL > wrote: > >> Hi All, >>

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

On Mon, 17 Apr 2017 at 08:23, ABHISHEK PALIWAL wrote: > Hi All, > > Here we have below steps to reproduce the issue > > Reproduction steps: > > > > root@128:~# gluster volume create brick 128.224.95.140:/tmp/brick force > - create the gluster volume > > volume

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

Hi All, Here we have below steps to reproduce the issue Reproduction steps: root@128:~# gluster volume create brick 128.224.95.140:/tmp/brick force - create the gluster volume volume create: brick: success: please start the volume to access data root@128:~# gluster volume set brick

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

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-devel] [Gluster-users] Glusterfs meta data space consumption issue

On Thu, Apr 13, 2017 at 12:19 PM, ABHISHEK PALIWAL wrote: > yes it is ext4. but what is the impact of this. > Did you have a lot of data before and you deleted all that data? ext4 if I remember correctly doesn't decrease size of directory once it expands it. So in ext4

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

yes it is ext4. but what is the impact of this. On Thu, Apr 13, 2017 at 9:26 AM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > Yes > > On Thu, Apr 13, 2017 at 8:21 AM, ABHISHEK PALIWAL > wrote: > >> Means the fs where this brick has been created? >> On Apr

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

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-devel] [Gluster-users] Glusterfs meta data space consumption issue

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-devel] [Gluster-users] Glusterfs meta data space consumption issue

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-devel] [Gluster-users] Glusterfs meta data space consumption issue

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-devel] [Gluster-users] Glusterfs meta data space consumption issue

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

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

Means if old data is present in brick and volume is not present then it should be visible in our brick dir /opt/lvmdir/c2/brick? On Fri, Apr 7, 2017 at 3:04 PM, Ashish Pandey wrote: > > If you are creating a fresh volume, then it is your responsibility to have > clean