search for: agsiz

...he file system, but it doesn?t seem to do that: # cat /proc/mdstat Personalities : [raid1] md10 : active raid1 sde[1] sdd[0] 499976512 blocks super 1.2 [2/2] [UU] bitmap: 0/4 pages [0KB], 65536KB chunk # 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 =ver...

...gt; > > # cat /proc/mdstat > Personalities : [raid1] > md10 : active raid1 sde[1] sdd[0] > 499976512 blocks super 1.2 [2/2] [UU] > bitmap: 0/4 pages [0KB], 65536KB chunk > > > # 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 swidt...

...>> Personalities : [raid1] >> md10 : active raid1 sde[1] sdd[0] >> 499976512 blocks super 1.2 [2/2] [UU] >> bitmap: 0/4 pages [0KB], 65536KB chunk >> >> >> # 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 >> =...

Hi, Thanks for your response, please find the xfs_info for each brick on the arbiter below: root at uk3-prod-gfs-arb-01:~# xfs_info /data/glusterfs/gv1/brick1 meta-data=/dev/sdc1 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 =...

...s are as follow: /dev/mapper/storage-samba_home on /samba_home type xfs (rw,relatime,attr2,delaylog,usrquota) /dev/mapper/storage-samba_share 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=...

...odesize, buf) == -1) + goto error; + } else if (p = strstr (lines[i], "agcount=")) { + buf = split_strdup (p + 8); + if (buf == NULL) goto error; + if (parse_uint32 (&ret->agcount, buf) == -1) + goto error; + } else if (p = strstr (lines[i], "agsize=")) { + buf = split_strdup (p + 7); + if (buf == NULL) goto error; + if (parse_uint32 (&ret->agsize, buf) == -1) + goto error; + } else if (p = strstr (lines[i], "sectsz=")) { + buf = split_strdup (p + 7); + if (buf == NULL) goto error; +...

...and on top of LVM. Filesystem was created using mkfs.xfs defaults with xfsprogs-2.9.4-1.el5.centos (that's the one that comes with 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=4...

...<liam.smith at ek.co> wrote: #yiv8784601153 P {margin-top:0;margin-bottom:0;}Hi, Thanks for your response, please find the xfs_info for each brick on the arbiter below: root at uk3-prod-gfs-arb-01:~# xfs_info /data/glusterfs/gv1/brick1meta-data=/dev/sdc1 ? ? ? ? ? ? ?isize=512 ? ?agcount=31, agsize=131007 blks? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ? sectsz=512 ? attr=2, projid32bit=1? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ? crc=1 ? ? ? ?finobt=1, sparse=1, rmapbt=0? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ? reflink=1data ? ? = ? ? ? ? ? ? ? ? ? ? ? bsize=4096 ? blocks=3931899, imaxpct=25? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ?...

...On Tuesday, July 4, 2023, 2:12 PM, Liam Smith <liam.smith at ek.co> wrote: Hi, Thanks for your response, please find the xfs_info for each brick on the arbiter below: root at uk3-prod-gfs-arb-01:~# xfs_info /data/glusterfs/gv1/brick1 meta-data=/dev/sdc1 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 =...

...#yiv0069265236 #yiv0069265236x_yiv8784601153 p {margin-top:0;margin-bottom:0;}-->Hi, Thanks for your response, please find the xfs_info for each brick on the arbiter below: root at uk3-prod-gfs-arb-01:~# xfs_info /data/glusterfs/gv1/brick1meta-data=/dev/sdc1 ? ? ? ? ? ? ?isize=512 ? ?agcount=31, agsize=131007 blks? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ? sectsz=512 ? attr=2, projid32bit=1? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ? crc=1 ? ? ? ?finobt=1, sparse=1, rmapbt=0? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ? reflink=1data ? ? = ? ? ? ? ? ? ? ? ? ? ? bsize=4096 ? blocks=3931899, imaxpct=25? ? ? ? ?= ? ? ? ? ? ? ? ? ? ? ?...

....md-cache-timeout: 600 performance.stat-prefetch: true performance.write-behind-window-size: 256MB server.event-threads: 8 transport.listen-backlog: 2048 root at gluster-host-01:~ # xfs_info /dev/mapper/gluster-storage-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 =versi...

...On Tuesday, July 4, 2023, 2:12 PM, Liam Smith <liam.smith at ek.co> wrote: Hi, Thanks for your response, please find the xfs_info for each brick on the arbiter below: root at uk3-prod-gfs-arb-01:~# xfs_info /data/glusterfs/gv1/brick1 meta-data=/dev/sdc1 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 =...

...lsblk shows... # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 32G 0 disk .... sdb 8:16 0 16G 0 disk ... so I can immediately... # mkfs.xfs /dev/sdb meta-data=/dev/sdb isize=256 agcount=4, agsize=1048576 blks ..... # mount /dev/sdb /mnt # (normally, I'd partition and lvm it, this is just for demo) I'm using a paravirtual scsi controller, and have previously installed open-vm-tools via yum. I then umounted it, and in vsphere deleted the vdisk and dmesg immediately shows... [155...

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

...PVj-1FVA-488x-Bs0K-ebQOmI And i can use it : [root at c7-pxe-install ~]# lvextend -L +640M vg0/lvRoot Extending logical volume lvRoot to 13.47 GiB Logical volume lvRoot successfully 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 ft...

...tat-prefetch: true > performance.write-behind-window-size: 256MB > server.event-threads: 8 > transport.listen-backlog: 2048 > > root at gluster-host-01:~ # xfs_info /dev/mapper/gluster-storage-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...

...tchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc, no SLP > uname -a Linux Ishtar 3.15.6-Isht-Van #1 SMP PREEMPT 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=...

...stat-prefetch: true > performance.write-behind-window-size: 256MB > server.event-threads: 8 > transport.listen-backlog: 2048 > > root at gluster-host-01:~ # xfs_info /dev/mapper/gluster-storage-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...

...MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 0 32G 0 disk > .... > sdb 8:16 0 16G 0 disk > ... > > so I can immediately... > > # mkfs.xfs /dev/sdb > meta-data=/dev/sdb isize=256 agcount=4, agsize=1048576 > blks > ..... > # mount /dev/sdb /mnt > # > > (normally, I'd partition and lvm it, this is just for demo) > I'm using a paravirtual scsi controller, and have previously installed > open-vm-tools via yum. > > I then umounted it, and in vsphere deleted...

Is there a way for a domU to discover size changes of block devices modified by dom0? To make it clear - if I do in dom0 a lvresize of a logical volume given as physical disk to a domU, is there a way to use the new size of this device within the domU without reboot? Thanks Ralf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com