search for: shchhv04

Displaying 4 results from an estimated 4 matches for "shchhv04".

Did you mean: shchhv01
2017 Dec 20
2
Upgrading from Gluster 3.8 to 3.12
...gt; Brick3: shchhv03-sto:/data/brick3/shchst01 > Brick4: shchhv01-sto:/data/brick1/shchst01 > Brick5: shchhv02-sto:/data/brick1/shchst01 > Brick6: shchhv03-sto:/data/brick1/shchst01 > Brick7: shchhv02-sto:/data/brick2/shchst01 > Brick8: shchhv03-sto:/data/brick2/shchst01 > Brick9: shchhv04-sto:/data/brick2/shchst01 > Brick10: shchhv02-sto:/data/brick4/shchst01 > Brick11: shchhv03-sto:/data/brick4/shchst01 > Brick12: shchhv04-sto:/data/brick4/shchst01 > Options Reconfigured: > cluster.data-self-heal-algorithm: full > features.shard-block-size: 512MB > features.sha...
2017 Dec 20
0
Upgrading from Gluster 3.8 to 3.12
...hchhv02-sto:/data/brick3/shchst01 Brick3: shchhv03-sto:/data/brick3/shchst01 Brick4: shchhv01-sto:/data/brick1/shchst01 Brick5: shchhv02-sto:/data/brick1/shchst01 Brick6: shchhv03-sto:/data/brick1/shchst01 Brick7: shchhv02-sto:/data/brick2/shchst01 Brick8: shchhv03-sto:/data/brick2/shchst01 Brick9: shchhv04-sto:/data/brick2/shchst01 Brick10: shchhv02-sto:/data/brick4/shchst01 Brick11: shchhv03-sto:/data/brick4/shchst01 Brick12: shchhv04-sto:/data/brick4/shchst01 Options Reconfigured: cluster.data-self-heal-algorithm: full features.shard-block-size: 512MB features.shard: enable performance.readdir-ahea...
2017 Dec 20
0
Upgrading from Gluster 3.8 to 3.12
...:/data/brick3/shchst01 >> Brick4: shchhv01-sto:/data/brick1/shchst01 >> Brick5: shchhv02-sto:/data/brick1/shchst01 >> Brick6: shchhv03-sto:/data/brick1/shchst01 >> Brick7: shchhv02-sto:/data/brick2/shchst01 >> Brick8: shchhv03-sto:/data/brick2/shchst01 >> Brick9: shchhv04-sto:/data/brick2/shchst01 >> Brick10: shchhv02-sto:/data/brick4/shchst01 >> Brick11: shchhv03-sto:/data/brick4/shchst01 >> Brick12: shchhv04-sto:/data/brick4/shchst01 >> Options Reconfigured: >> cluster.data-self-heal-algorithm: full >> features.shard-block-size:...
2017 Dec 19
2
Upgrading from Gluster 3.8 to 3.12
I have not done the upgrade yet. Since this is a production cluster I need to make sure it stays up or schedule some downtime if it doesn't doesn't. Thanks. On Tue, Dec 19, 2017 at 10:11 AM, Atin Mukherjee <amukherj at redhat.com> wrote: > > > On Tue, Dec 19, 2017 at 1:10 AM, Ziemowit Pierzycki <ziemowit at pierzycki.com> > wrote: >> >> Hi, >>