Re: [PATCH] Fix hang of gfs2 mount if older dlm_controld is used

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

 



On Fri, Sep 27, 2013 at 3:38 AM, Steven Whitehouse <swhiteho@xxxxxxxxxx> wrote:
> Hi,
>
> On Thu, 2013-09-26 at 14:05 -0400, David Teigland wrote:
>> On Thu, Sep 26, 2013 at 12:24:49PM -0500, Goldwyn Rodrigues wrote:
>> > This folds ops_results and error into one. This enables the
>> > error code to trickle all the way to the calling function and the gfs2
>> > mount fails if older dlm_controld is used.
>>
>> If it's not working then I'd prefer to fix it rather than abandoning the
>> idea of making it work.
>> Dave
>>
>
> I agree. I use the older dlm_controld regularly and I've not seen any
> obvious issues. What is the problem in this case I wonder?
>


Sorry, I misread the code. The dlm_new_lockspace() still continues to
create a new lockspace even if the operations are not provided. So,
the fallback option has to be after that rather than calling the
function again.


-- 
Goldwyn

-- 
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster




[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux