search for: imaxpct

...# mkfs.xfs /dev/md10p2 meta-data=/dev/md10p2 isize=512 agcount=4, agsize=30199892 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=0, sparse=0 data = bsize=4096 blocks=120799568, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=58984, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none...

...isize=512 agcount=31, agsize=131007 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 data = bsize=4096 blocks=3931899, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none...

Hi Liam, I saw that your XFS uses ?imaxpct=25? which for an arbiter brick is a little bit low. If you have free space on the bricks, increase the maxpct to a bigger value, like:xfs_growfs -m 80 /path/to/brickThat will set 80% of the Filesystem for inodes, which you can verify with df -i /brick/path (compare before and after).?This way?you w...

...gluster.org <gluster-users at gluster.org> Subject: Re: [Gluster-users] remove_me files building up CAUTION: This e-mail originates from outside of Ekco. Do not click links or attachments unless you recognise the sender. ________________________________ Hi Liam, I saw that your XFS uses ?imaxpct=25? which for an arbiter brick is a little bit low. If you have free space on the bricks, increase the maxpct to a bigger value, like: xfs_growfs -m 80 /path/to/brick That will set 80% of the Filesystem for inodes, which you can verify with df -i /brick/path (compare before and after). This way yo...

...> meta-data=/dev/md10p2 isize=512 agcount=4, agsize=30199892 > blks > = sectsz=512 attr=2, projid32bit=1 > = crc=1 finobt=0, sparse=0 > data = bsize=4096 blocks=120799568, imaxpct=25 > = sunit=0 swidth=0 blks > naming =version 2 bsize=4096 ascii-ci=0 ftype=1 > log =internal log bsize=4096 blocks=58984, version=2 > = sectsz=512 sunit=0 blks, lazy-count=1 > rea...

...dev/md10p2 isize=512 agcount=4, agsize=30199892 >> blks >> = sectsz=512 attr=2, projid32bit=1 >> = crc=1 finobt=0, sparse=0 >> data = bsize=4096 blocks=120799568, imaxpct=25 >> = sunit=0 swidth=0 blks >> naming =version 2 bsize=4096 ascii-ci=0 ftype=1 >> log =internal log bsize=4096 blocks=58984, version=2 >> = sectsz=512 sunit=0 blks, lazy-...

...hare on /samba_share type xfs (rw,relatime,attr2,delaylog,usrquota) sudo xfs_info /samba_home/ meta-data=/dev/mapper/storage-samba_home isize=256 agcount=24, agsize=32768000 blks = sectsz=512 attr=2 data = bsize=4096 blocks=757405696, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 log =internal bsize=4096 blocks=32768, version=2 = sectsz=512 sunit=0 blks, lazy-count=0 realtime =none ext...

...ek.co>; gluster-users at gluster.org <gluster-users at gluster.org> Subject: Re: [Gluster-users] remove_me files building up? | CAUTION:?This e-mail originates from outside of Ekco. Do not click links or attachments unless you recognise the sender. | Hi Liam, I saw that your XFS uses ?imaxpct=25? which for an arbiter brick is a little bit low. If you have free space on the bricks, increase the maxpct to a bigger value, like:xfs_growfs -m 80 /path/to/brickThat will set 80% of the Filesystem for inodes, which you can verify with df -i /brick/path (compare before and after).?This way?you w...

...goto error; + else if (i == 5) + if (parse_uint32 (&ret->logblocks, buf) == -1) + goto error; + else if (i == 7) + if (parse_uint64 (&ret->rtblocks, buf) == -1) + goto error; + else goto error; + } else if (p = strstr (lines[i], "imaxpct=")) { + buf = split_strdup (p + 8); + if (buf == NULL) goto error; + if (parse_uint32 (&ret->imaxpct, buf) == -1) + goto error; + } else if (p = strstr (lines[i], "sunit=")) { + buf = split_strdup (p + 6); + if (buf == NULL) goto error; +...

...CentOS 5.x by default.) These are the defaults with which the filesystem was created: # xfs_info /store meta-data=/dev/sda5????????????? isize=256??? agcount=32, agsize=7454720 blks ???????? =?????????????????????? sectsz=512?? attr=0 data???? =?????????????????????? bsize=4096?? blocks=238551040, imaxpct=25 ???????? =?????????????????????? sunit=0????? swidth=0 blks, unwritten=1 naming?? =version 2????????????? bsize=4096 log????? =internal?????????????? bsize=4096?? blocks=32768, version=1 ???????? =?????????????????????? sectsz=512?? sunit=0 blks, lazy-count=0 realtime =none?????????????????? ext...

.../disco1TB-1/vms gluster2:/disco1TB-1/vms So I went ahead and installed a Debian 12 and installed the same gluster version that the other servers, which is now 11.1 or something like that. In this new server, I have a small disk like 480G in size. And I created 3 partitions formatted with XFS using imaxpct=75, as suggested in previous emails. And than in the gluster nodes, I tried to add the brick gluster vol add-brick VMS replica 3 arbiter 1 arbiter:/arbiter1/arbiter1 arbiter:/arbiter2/arbiter2 arbiter:/arbiter3/arbiter3 But to my surprise (or not!) I got this message: volume add-brick: failed: Mu...

...gluster.org <gluster-users at gluster.org> Subject: Re: [Gluster-users] remove_me files building up CAUTION: This e-mail originates from outside of Ekco. Do not click links or attachments unless you recognise the sender. ________________________________ Hi Liam, I saw that your XFS uses ?imaxpct=25? which for an arbiter brick is a little bit low. If you have free space on the bricks, increase the maxpct to a bigger value, like: xfs_growfs -m 80 /path/to/brick That will set 80% of the Filesystem for inodes, which you can verify with df -i /brick/path (compare before and after). This way yo...

...o1TB-1/vms > > So I went ahead and installed a Debian 12 and installed the same > gluster version that the other servers, which is now 11.1 or > something like that. > In this new server, I have a small disk like 480G in size. > And I created 3 partitions?formatted?with XFS using?imaxpct=75, as > suggested in previous emails. > > And than in the gluster nodes, I tried to add the brick > gluster vol add-brick VMS replica 3 arbiter 1 > arbiter:/arbiter1/arbiter1 arbiter:/arbiter2/arbiter2 > arbiter:/arbiter3/arbiter3 > > But to my surprise (or not!) I got th...

...:/disco1TB-1/vms > > So I went ahead and installed a Debian 12 and installed the same gluster > version that the other servers, which is now 11.1 or something like that. > In this new server, I have a small disk like 480G in size. > And I created 3 partitions formatted with XFS using imaxpct=75, as > suggested in previous emails. > > And than in the gluster nodes, I tried to add the brick > gluster vol add-brick VMS replica 3 arbiter 1 arbiter:/arbiter1/arbiter1 > arbiter:/arbiter2/arbiter2 arbiter:/arbiter3/arbiter3 > > But to my surprise (or not!) I got this mess...

...unlocked meta-data=/dev/mapper/gluster-storage-unlocked isize=512 agcount=4, agsize=196607360 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=0 spinodes=0 data = bsize=4096 blocks=786429440, imaxpct=5 = sunit=0 swidth=0 blks naming =version 2 bsize=8192 ascii-ci=0 ftype=1 log =internal bsize=4096 blocks=383998, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none...

Hi, you mentioned that the arbiter bricks run out of inodes.Are you using XFS ?Can you provide the xfs_info of each brick ? Best Regards,Strahil Nikolov? On Sat, Jul 1, 2023 at 19:41, Liam Smith<liam.smith at ek.co> wrote: Hi, We're running a cluster with two data nodes and one arbiter, and have sharding enabled. We had an issue a while back where one of the server's

...uccessfully resized [root at c7-pxe-install ~]# xfs_growfs / meta-data=/dev/mapper/vg0-lvRoot isize=256 agcount=4, agsize=841728 blks = sectsz=512 attr=2, projid32bit=1 = crc=0 data = bsize=4096 blocks=3366912, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=0 log =internal bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none ext...

...d installed a Debian 12 and installed the same > > > gluster version that the other servers, which is now 11.1 or > > > something like that. > > > In this new server, I have a small disk like 480G in size. > > > And I created 3 partitions?formatted?with XFS using?imaxpct=75, > > > as suggested in previous emails. > > > > > > And than in the gluster nodes, I tried to add the brick > > > gluster vol add-brick VMS replica 3 arbiter 1 > > > arbiter:/arbiter1/arbiter1 arbiter:/arbiter2/arbiter2 > > > arbiter:/arbite...

.../mapper/gluster-storage-unlocked isize=512 ? ?agcount=4, > agsize=196607360 blks > ? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ? sectsz=512 ? attr=2, projid32bit=1 > ? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ? crc=1 ? ? ? ?finobt=0 spinodes=0 > data ? ? = ? ? ? ? ? ? ? ? ? ? ? bsize=4096 ? blocks=786429440, imaxpct=5 > ? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ? sunit=0 ? ? ?swidth=0 blks > naming ? =version 2 ? ? ? ? ? ? ?bsize=8192 ? ascii-ci=0 ftype=1 > log ? ? ?=internal ? ? ? ? ? ? ? bsize=4096 ? blocks=383998, version=2 > ? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ? sectsz=512 ? sunit=0 blks, lazy-count=1 > r...

...Sat Jul 19 12:31:28 PDT 2014 x86_64 x86_64 x86_64 GNU/Linux File system info: > xfs_info /home meta-data=/dev/mapper/Data-Home isize=512 agcount=32, agsize=12582896 blks = sectsz=4096 attr=2 data = bsize=4096 blocks=402652672, imaxpct=5 = sunit=16 swidth=16 blks naming =version 2 bsize=4096 ascii-ci=0 log =internal bsize=4096 blocks=32768, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none ext...