Re: heal info reporting not connected after replacebrick

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 <alan@xxxxxxxxxxx> 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

________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/441850968

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux