Strahil
2019-Nov-26 18:37 UTC
[Gluster-users] heal info reporting not connected after replacebrick
You can try to force start the volume via: gluster volume start <vol> force And then check again. Best Regards, Strahil NikolovOn Nov 26, 2019 18:50, Alan <alan at griff.me.uk> wrote:> > Hi, > > Due to work on the host disk subsystem I had to replace a brick on a replicated volume. The replace seems to have worked ok as "vol status" reports the new brick up and heal has completed. But when I run vol heal <vol> info the status of the new brick is "Transport endpoint is not connected". > > Is this something to worry about? > > Version: 3.12.15. > > Thanks, > > Alan >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20191126/336c252a/attachment.html>
Alan
2019-Nov-26 19:11 UTC
[Gluster-users] heal info reporting not connected after replacebrick
Actually, it resolved its self after a few hours. Thanks, Alan ---- On Tue, 26 Nov 2019 18:37:10 +0000 Strahil <mailto:hunter86_bg at yahoo.com> wrote ---- You can try to force start the volume via: gluster volume start <vol> force And then check again. Best Regards, Strahil Nikolov On Nov 26, 2019 18:50, Alan <mailto:alan at griff.me.uk> wrote: Hi, Due to work on the host disk subsystem I had to replace a brick on a replicated volume. The replace seems to have worked ok as "vol status" reports the new brick up and heal has completed. But when I run vol heal <vol> info the status of the new brick is "Transport endpoint is not connected". Is this something to worry about? Version: 3.12.15. Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20191126/b308ef3b/attachment.html>