Am 04.04.2016 um 19:42 schrieb Niels de Vos:
On Mon, Apr 04, 2016 at 05:08:26PM +0200, Patrick Matthäi wrote:
Am 04.04.2016 um 15:23 schrieb Kaleb KEITHLEY:
On 04/04/2016 09:11 AM, Kaleb KEITHLEY wrote:
On 04/04/2016 07:41 AM, Niels de Vos wrote:
On Fri, Apr 01, 2016 at 09:56:45AM +0530, Atin Mukherjee wrote:
Hi Kaushal,
We hit a regression yesterday where GlusterD fails to restart when the
volume has snapshots. Refer to [1] for more details. The work around is
also a bit tedious where each snapshot brick folders have to be created
manually and I don't think see any other alternative workaround here.
IMO, we should mention this as known issue in the release note for 3.7.10.
This sounds serious enough to not package 3.7.10 and have users update
to it automatically.
That djinni is already out of the bottle.
If there's a fix available then it seems (to me) that a better path
forward is to release 3.7.11 quickly.
--
I would support it, since I already uploaded it to Debian:
https://packages.qa.debian.org/g/glusterfs.html
I am not planning to do a 3.5.x release next week (expected around the
10th of each month), there are no patches yet. We could use this release
date for the corrected 3.7.11. Or even pull it forward as soon as a
patch is available.
Niels
Oh no, I also just mean the 3.7.11 release, since I have uploaded 3.7.10
already
_______________________________________________
packaging mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/packaging
