search for: 910d

...hostId='4c89baa5-e8f7-4132-a4b3-af332247570c'}), log id: 7fce25d3 2017-07-24 15:54:02,209+02 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler2) [b7590c4] Could not associate brick 'gdnode01:/gluster/engine/brick' of volume 'd19c19e3-910d-437b-8ba7- 4f2a23d17515' with correct network as no gluster network found in cluster '00000002-0002-0002-0002-00000000017a' 2017-07-24 15:54:02,212+02 WARN [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler2) [b7590c4] Could not associate brick ...

...8f7-4132-a4b3-af332247570c'}), log id: 7fce25d3 > 2017-07-24 15:54:02,209+02 WARN [org.ovirt.engine.core.vdsbro > ker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler2) [b7590c4] > Could not associate brick 'gdnode01:/gluster/engine/brick' of volume > 'd19c19e3-910d-437b-8ba7-4f2a23d17515' with correct network as no gluster > network found in cluster '00000002-0002-0002-0002-00000000017a' > 2017-07-24 15:54:02,212+02 WARN [org.ovirt.engine.core.vdsbro > ker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler2) [b7590c4] > Could n...

...*features.shard-block-size: 512MB* > *network.ping-timeout: 30* > *performance.strict-o-direct: on* > *cluster.granular-entry-heal: on* > *auth.allow: ** > *server.allow-insecure: on* > > > > > > *Volume Name: engine* > *Type: Replicate* > *Volume ID: d19c19e3-910d-437b-8ba7-4f2a23d17515* > *Status: Started* > *Snapshot Count: 0* > *Number of Bricks: 1 x 3 = 3* > *Transport-type: tcp* > *Bricks:* > *Brick1: gdnode01:/gluster/engine/brick* > *Brick2: gdnode02:/gluster/engine/brick* > *Brick3: gdnode04:/gluster/engine/brick* > *Option...

...B/ > /network.ping-timeout: 30/ > /performance.strict-o-direct: on/ > /cluster.granular-entry-heal: on/ > /auth.allow: */ > /server.allow-insecure: on/ > > > > > > /Volume Name: engine/ > /Type: Replicate/ > /Volume ID: d19c19e3-910d-437b-8ba7-4f2a23d17515/ > /Status: Started/ > /Snapshot Count: 0/ > /Number of Bricks: 1 x 3 = 3/ > /Transport-type: tcp/ > /Bricks:/ > /Brick1: gdnode01:/gluster/engine/brick/ > /Brick2: gdnode02:/gluster/engine/brick/ > /Brick3: gdnode04:/gl...

...oblem you are seeing. > Hi, You talking about errors like these? 2017-07-24 15:54:02,209+02 WARN [org.ovirt.engine.core.vdsbro ker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler2) [b7590c4] Could not associate brick 'gdnode01:/gluster/engine/brick' of volume 'd19c19e3-910d-437b-8ba7-4f2a23d17515' with correct network as no gluster network found in cluster '00000002-0002-0002-0002-00000000017a' How to assign "glusternw (???)" to the correct interface? Other errors on unsync gluster elements still remain... This is a production env, so, there i...

On 07/19/2017 08:02 PM, Sahina Bose wrote: > [Adding gluster-users] > > On Wed, Jul 19, 2017 at 2:52 PM, yayo (j) <jaganz at gmail.com > <mailto:jaganz at gmail.com>> wrote: > > Hi all, > > We have an ovirt cluster hyperconverged with hosted engine on 3 > full replicated node . This cluster have 2 gluster volume: > > - data: volume for

...nd on all 3 nodes > 2. Are these 12 files also present in the 3rd data brick? > I've checked right now: all files exists in all 3 nodes > 3. Can you provide the output of `gluster volume info` for the this volume? > *Volume Name: engine* *Type: Replicate* *Volume ID: d19c19e3-910d-437b-8ba7-4f2a23d17515* *Status: Started* *Snapshot Count: 0* *Number of Bricks: 1 x 3 = 3* *Transport-type: tcp* *Bricks:* *Brick1: node01:/gluster/engine/brick* *Brick2: node02:/gluster/engine/brick* *Brick3: node04:/gluster/engine/brick* *Options Reconfigured:* *nfs.disable: on* *performance.rea...

...gt; > You talking about errors like these? > > 2017-07-24 15:54:02,209+02 WARN [org.ovirt.engine.core.vdsbro > ker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler2) [b7590c4] > Could not associate brick 'gdnode01:/gluster/engine/brick' of volume > 'd19c19e3-910d-437b-8ba7-4f2a23d17515' with correct network as no gluster > network found in cluster '00000002-0002-0002-0002-00000000017a' > > > How to assign "glusternw (???)" to the correct interface? > https://www.ovirt.org/blog/2017/04/up-and-running-with-ovirt-4.1-and-g...

...eatures.shard: on* *user.cifs: off* *storage.owner-gid: 36* *features.shard-block-size: 512MB* *network.ping-timeout: 30* *performance.strict-o-direct: on* *cluster.granular-entry-heal: on* *auth.allow: ** *server.allow-insecure: on* *Volume Name: engine* *Type: Replicate* *Volume ID: d19c19e3-910d-437b-8ba7-4f2a23d17515* *Status: Started* *Snapshot Count: 0* *Number of Bricks: 1 x 3 = 3* *Transport-type: tcp* *Bricks:* *Brick1: gdnode01:/gluster/engine/brick* *Brick2: gdnode02:/gluster/engine/brick* *Brick3: gdnode04:/gluster/engine/brick* *Options Reconfigured:* *nfs.disable: on* *performan...

2017-07-20 14:48 GMT+02:00 Ravishankar N <ravishankar at redhat.com>: > > But it does say something. All these gfids of completed heals in the log > below are the for the ones that you have given the getfattr output of. So > what is likely happening is there is an intermittent connection problem > between your mount and the brick process, leading to pending heals again >

...in the 3rd data brick? > > > I've checked right now: all files exists in all 3 nodes > > 3. Can you provide the output of `gluster volume info` for the > this volume? > > > > /Volume Name: engine/ > /Type: Replicate/ > /Volume ID: d19c19e3-910d-437b-8ba7-4f2a23d17515/ > /Status: Started/ > /Snapshot Count: 0/ > /Number of Bricks: 1 x 3 = 3/ > /Transport-type: tcp/ > /Bricks:/ > /Brick1: node01:/gluster/engine/brick/ > /Brick2: node02:/gluster/engine/brick/ > /Brick3: node04:/gluster/...

[Adding gluster-users] On Wed, Jul 19, 2017 at 2:52 PM, yayo (j) <jaganz at gmail.com> wrote: > Hi all, > > We have an ovirt cluster hyperconverged with hosted engine on 3 full > replicated node . This cluster have 2 gluster volume: > > - data: volume for the Data (Master) Domain (For vm) > - engine: volume fro the hosted_storage Domain (for hosted engine) > >

...n the 3rd data brick? >> > > I've checked right now: all files exists in all 3 nodes > > >> 3. Can you provide the output of `gluster volume info` for the this >> volume? >> > > > *Volume Name: engine* > *Type: Replicate* > *Volume ID: d19c19e3-910d-437b-8ba7-4f2a23d17515* > *Status: Started* > *Snapshot Count: 0* > *Number of Bricks: 1 x 3 = 3* > *Transport-type: tcp* > *Bricks:* > *Brick1: node01:/gluster/engine/brick* > *Brick2: node02:/gluster/engine/brick* > *Brick3: node04:/gluster/engine/brick* > *Options Reco...

...ight now: all files exists in all 3 nodes >> >> 3. Can you provide the output of `gluster volume info` for >> the this volume? >> >> >> >> /Volume Name: engine/ >> /Type: Replicate/ >> /Volume ID: d19c19e3-910d-437b-8ba7-4f2a23d17515/ >> /Status: Started/ >> /Snapshot Count: 0/ >> /Number of Bricks: 1 x 3 = 3/ >> /Transport-type: tcp/ >> /Bricks:/ >> /Brick1: node01:/gluster/engine/brick/ >> /Brick2: node02:/...