[Gluster-Maintainers] 3.7.10 known issue

[Atin Mukherjee]

On 04/04/2016 08:21 PM, Vijay Bellur wrote:
> On 04/04/2016 10:49 AM, Atin Mukherjee wrote:
>>
>>
>> On 04/04/2016 07:43 PM, Atin Mukherjee wrote:
>>>
>>>
>>> On 04/04/2016 06:53 PM, Kaleb KEITHLEY wrote:
>>>> 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.
>> One correction here, the issue is seen only when the node reboots, not
>> glusterd. Considering that users won't reboot machines often, we can
>> still live with it for the next scheduled release? I'll be working on
>> the release note to put down the work around.
> 
> Would it be possible to provide a script to make it less tedious for
> administrators?
I think we should be able to come up with a script as the snap brick
path also gets persisted and the script can iterate over all such files,
parse the brick path and do a mkdir -p. I'll confirm this with
Rajesh/Avra and get back.

~Atin
> 
> -Vijay
> 
> 
>