[Bugs] [Bug 1366813] Second gluster volume is offline after daemon restart or server reboot

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1366813



--- Comment #6 from Kaushal <kaushal at redhat.com> ---
(Adding a hopefully friendlier description of the problem)

On restarting GlusterD or rebooting a GlusterFS server, only the bricks of the
first volume get started. The bricks of the remaining volumes are not started.
This is a regression caused by a change in GlusterFS-3.8.2.

Because of this regression, GlusterFS volumes will be left in an inoperable
state after upgrading to 3.8.2, as upgrading involves restarting GlusterD.
Users can forcefully start the remaining volumes, by doing running the `gluster
volume start <name> force` command.

Also, this breaks automatic start of volumes on rebooting servers, and leaves
the volumes inoperable.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=z1cNgcGM1Z&a=cc_unsubscribe