search for: gluster2

Sure! > 1 - output of gluster volume heal <volname> info Brick pod-sjc1-gluster1:/data/brick1/gv0 Status: Connected Number of entries: 0 Brick pod-sjc1-gluster2:/data/brick1/gv0 Status: Connected Number of entries: 0 Brick pod-sjc1-gluster1:/data/brick2/gv0 Status: Connected Number of entries: 0 Brick pod-sjc1-gluster2:/data/brick2/gv0 Status: Connected Number of entries: 0 Brick pod-sjc1-gluster1:/data/brick3/gv0 Status: Connected Number of entries: 0...

...erfs, although I didn't find detailed documentation about it. (I'm using glusterfs 3.10.8) So my question is: can I really use glusterfs to do failover in the way described below, or am I misusing glusterfs? (and potentially corrupting my data?) My setup is: I have two servers (qlogin and gluster2) that access a shared SAN storage. Both servers connect to the same SAN (SAS multipath) and I implement locking via lvm2 and sanlock, so I can mount the same storage on either server. The idea is that normally each server serves one brick, but in case one server fails, the other server can serve b...

...lar effect? On Thu, Dec 21, 2017 at 11:44 AM, Tom Fite <tomfite at gmail.com> wrote: > Sure! > > > 1 - output of gluster volume heal <volname> info > > Brick pod-sjc1-gluster1:/data/brick1/gv0 > Status: Connected > Number of entries: 0 > > Brick pod-sjc1-gluster2:/data/brick1/gv0 > Status: Connected > Number of entries: 0 > > Brick pod-sjc1-gluster1:/data/brick2/gv0 > Status: Connected > Number of entries: 0 > > Brick pod-sjc1-gluster2:/data/brick2/gv0 > Status: Connected > Number of entries: 0 > > Brick pod-sjc1-gluster1...

The sizes of the files are extremely varied, there are millions of small (<1 MB) files and thousands of files larger than 1 GB. Attached is the tier log for gluster1 and gluster2. These are full of "demotion failed" messages, which is also shown in the status: [root at pod-sjc1-gluster1 gv0]# gluster volume tier gv0 status Node Promoted files Demoted files Status run time in h:m:s --------- --------- ---...

...find detailed documentation about it. (I'm using glusterfs 3.10.8) > > So my question is: can I really use glusterfs to do failover in the way > described below, or am I misusing glusterfs? (and potentially corrupting my > data?) > > My setup is: I have two servers (qlogin and gluster2) that access a shared > SAN storage. Both servers connect to the same SAN (SAS multipath) and I > implement locking via lvm2 and sanlock, so I can mount the same storage on > either server. > The idea is that normally each server serves one brick, but in case one > server fails, the...

...s are extremely varied, there are millions of small >> (<1 MB) files and thousands of files larger than 1 GB. The tier use case is for bigger size files. not the best for files of smaller size. That can end up hindering the IOs. >> >> Attached is the tier log for gluster1 and gluster2. These are full of >> "demotion failed" messages, which is also shown in the status: >> >> [root at pod-sjc1-gluster1 gv0]# gluster volume tier gv0 status >> Node Promoted files Demoted files Status >> run time in h:m:s >> -...

...39;'s our stripe client setup : #### volume client-stripe-1 type protocol/client option transport-type ib-verbs option remote-host gluster1 option remote-subvolume iothreads end-volume volume client-stripe-2 type protocol/client option transport-type ib-verbs option remote-host gluster2 option remote-subvolume iothreads end-volume volume client-stripe-3 type protocol/client option transport-type ib-verbs option remote-host gluster3 option remote-subvolume iothreads end-volume volume client-stripe-4 type protocol/client option transport-type ib-verbs option remote...

...nt on files are blocked? On Wed, Jan 10, 2018 at 10:17 AM, Tom Fite <tomfite at gmail.com> wrote: > The sizes of the files are extremely varied, there are millions of small > (<1 MB) files and thousands of files larger than 1 GB. > > Attached is the tier log for gluster1 and gluster2. These are full of > "demotion failed" messages, which is also shown in the status: > > [root at pod-sjc1-gluster1 gv0]# gluster volume tier gv0 status > Node Promoted files Demoted files Status > run time in h:m:s > ---------...

...n't find detailed documentation about it. (I'm using glusterfs 3.10.8) > > So my question is: can I really use glusterfs to do failover in the way described below, or am I misusing glusterfs? (and potentially corrupting my data?) > > My setup is: I have two servers (qlogin and gluster2) that access a shared SAN storage. Both servers connect to the same SAN (SAS multipath) and I implement locking via lvm2 and sanlock, so I can mount the same storage on either server. > The idea is that normally each server serves one brick, but in case one server fails, the other server can ser...

Hi, Can you send the volume info, and volume status output and the tier logs. And I need to know the size of the files that are being stored. On Tue, Jan 9, 2018 at 9:51 PM, Tom Fite <tomfite at gmail.com> wrote: > I've recently enabled an SSD backed 2 TB hot tier on my 150 TB 2 server / 3 > bricks per server distributed replicated volume. > > I'm seeing IO get blocked

...ive hot tier: [root at pod-sjc1-gluster1 ~]# gluster volume info Volume Name: gv0 Type: Tier Volume ID: d490a9ec-f9c8-4f10-a7f3-e1b6d3ced196 Status: Started Snapshot Count: 13 Number of Bricks: 8 Transport-type: tcp Hot Tier : Hot Tier Type : Replicate Number of Bricks: 1 x 2 = 2 Brick1: pod-sjc1-gluster2:/data/hot_tier/gv0 Brick2: pod-sjc1-gluster1:/data/hot_tier/gv0 Cold Tier: Cold Tier Type : Distributed-Replicate Number of Bricks: 3 x 2 = 6 Brick3: pod-sjc1-gluster1:/data/brick1/gv0 Brick4: pod-sjc1-gluster2:/data/brick1/gv0 Brick5: pod-sjc1-gluster1:/data/brick2/gv0 Brick6: pod-sjc1-gluster2:/d...

...--- Here's the client configuration: volume client-stripe-1 type protocol/client option transport-type ib-verbs option remote-host gluster1 option remote-subvolume iothreads end-volume volume client-stripe-2 type protocol/client option transport-type ib-verbs option remote-host gluster2 option remote-subvolume iothreads end-volume volume client-stripe-3 type protocol/client option transport-type ib-verbs option remote-host gluster3 option remote-subvolume iothreads end-volume volume client-stripe-4 type protocol/client option transport-type ib-verbs option remote...

Could youplease provide following - 1 - output of gluster volume heal <volname> info 2 - /var/log/glusterfs - provide log file with mountpoint-volumename.log 3 - output of gluster volume <volname> info 4 - output of gluster volume <volname> status 5 - Also, could you try unmount the volume and mount it again and check the size? ----- Original Message ----- From:

...ume: gfs_vms Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gluster1.linova.de:/glusterfs/sde1enc /brick 58448 0 Y 1062218 Brick gluster2.linova.de:/glusterfs/sdc1enc /brick 50254 0 Y 20596 Brick gluster3.linova.de:/glusterfs/sdc1enc /brick 52840 0 Y 1627513 Brick gluster1.linova.de:/glusterfs/sdf1enc /brick...

I have a glusterfs setup with distributed disperse volumes 5 * ( 4 + 2 ). After a server crash, "gluster peer status" reports all peers as connected. "gluster volume status detail" shows that all bricks are up and running with the right size, but when I use df from a client mount point, the size displayed is about 1/6 of the total size. When browsing the data, they seem to

...volume: gfs_vms Gluster process? ? ? ? ? ? ? ? ? ? ? ? ? ? TCP Port? RDMA Port? Online? Pid ------------------------------------------------------------------------------ Brick gluster1.linova.de:/glusterfs/sde1enc /brick? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 58448? ? 0? ? ? ? ? Y? ? ? 1062218 Brick gluster2.linova.de:/glusterfs/sdc1enc /brick? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 50254? ? 0? ? ? ? ? Y? ? ? 20596 Brick gluster3.linova.de:/glusterfs/sdc1enc /brick? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 52840? ? 0? ? ? ? ? Y? ? ? 1627513 Brick gluster1.linova.de:/glusterfs/sdf1enc /brick? ? ? ? ? ? ? ? ? ?...

...n like: systemctl enable glusterfsmounts.service systemctl demon-reload Also, I am using /etc/fstab to mount the glusterfs mount point properly, since the Proxmox GUI seems to me a little broken in this regards gluster1:VMS1 /vms1 glusterfs defaults,_netdev,x-systemd.automount,backupvolfile-server=gluster2 0 0 --- Gilberto Nunes Ferreira (47) 99676-7530 - Whatsapp / Telegram Em qua., 7 de jun. de 2023 ?s 01:51, Strahil Nikolov <hunter86_bg at yahoo.com> escreveu: > Hi Chris, > > here is a link to the settings needed for VM storage: > https://github.com/gluster/glusterfs/blob...

...ume: gfs_vms Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick gluster1.linova.de:/glusterfs/sde1enc /brick 58448 0 Y 1062218 Brick gluster2.linova.de:/glusterfs/sdc1enc /brick 50254 0 Y 20596 Brick gluster3.linova.de:/glusterfs/sdc1enc /brick 52840 0 Y 1627513 Brick gluster1.linova.de:/glusterfs/sdf1enc /brick...

...process TCP Port RDMA Port Online Pid > ------------------------------------------------------------------------------ > Brick gluster1.linova.de:/glusterfs/sde1enc > /brick 58448 0 Y 1062218 > Brick gluster2.linova.de:/glusterfs/sdc1enc > /brick 50254 0 Y 20596 > Brick gluster3.linova.de:/glusterfs/sdc1enc > /brick 52840 0 Y 1627513 > Brick gluster1.linova.de:/glusterfs/sdf1enc &g...

I've recently enabled an SSD backed 2 TB hot tier on my 150 TB 2 server / 3 bricks per server distributed replicated volume. I'm seeing IO get blocked across all client FUSE threads for 10 to 15 seconds while the promotion daemon runs. I see the 'glustertierpro' thread jump to 99% CPU usage on both boxes when these delays occur and they happen every 25 minutes (my