[Samba] CTDB and NFS4

J. Echter j.echter at echter-kuechen-elektro.de
Tue Mar 11 06:33:05 MDT 2014


Am 11.03.2014 09:47, schrieb Stephen Ward:
> Hi L.P.H van Belle,
>
> Thank you for your suggestion, as NFS4 is already working and it is just
> the clustering setup that I am having issues with I'm not sure if this
> would still help?
>
>
> On Tue, Mar 11, 2014 at 9:30 PM, L.P.H. van Belle <belle at bazuin.nl> wrote:
>
>> only thing in know for NFSv4
>> add in krb5.conf in
>> [libdefaults]
>> allow_weak_crypto = true
>>
>> then nfs4v wil work. ( tested in a non CTDB setup )
>>
>>
>>
>>
>>
>>> -----Oorspronkelijk bericht-----
>>> Van: sw_samba at nzgeek.com
>>> [mailto:samba-bounces at lists.samba.org] Namens Stephen Ward
>>> Verzonden: dinsdag 11 maart 2014 9:09
>>> Aan: Volker.Lendecke at sernet.de
>>> CC: samba at lists.samba.org
>>> Onderwerp: Re: [Samba] CTDB and NFS4
>>>
>>> Hi Volker, thank you for your comments.
>>>
>>> Using CTDB with an NFS server if I mount with the version 3 option then
>>> stop ctdb on the server the client fails over to the new
>>> server fine.  Same
>>> client, same servers, same process but mounting with the
>>> version 4 option
>>> and when CTDB fails over the client locks.  After ten minutes or so I
>>> killed the process on the client, it was still not responsive.
>>>
>>> As I understand it this works because the NFS daemons share records and
>>> 'tickle' connections on failover (see
>>> https://wiki.samba.org/index.php/CTDB_Setup#Setting_up_CTDB_for
>>> _clustered_NFS
>>> ).
>>>
>>> NFS4 works fine except for failover and NFS3 works fine
>>> including failover
>>> so I assume that it is specifically an issue with NFS4 with CTDB.
>>>
>>> My understanding of specifically how this works is limited so
>>> if anyone has
>>> any ideas about this at all I'd be really keen to hear!
>>>
>>>
>>> On Tue, Mar 11, 2014 at 8:30 PM, Volker Lendecke
>>> <Volker.Lendecke at sernet.de>wrote:
>>>
>>>> On Fri, Mar 07, 2014 at 12:32:01PM +1300, Stephen Ward wrote:
>>>>> I'm sorry if this has already been covered somewhere, but
>>> I've had a look
>>>>> and can't find it.  Also if there is a better place for
>>> this question,
>>>>> please let me know.
>>>>>
>>>>> I know that the CTDB documentation states that only NFS2/3
>>> are supported
>>>>> with CTDB but what I'd really like to know is why NFS4
>>> won't work and if
>>>>> NFS4 support is planned for the future (timeline?).  Also
>>> can anyone
>>>>> suggest any work arounds/development versions/anything
>>> that may help with
>>>>> this?
>>>>>
>>>>> I have a cluster that works well with samba4 and NFS3 (on
>>> GPFS/RHEL) but
>>>>> unsurprisingly, while NFS4 works ok normally, if I stop
>>> the server a
>>>> client
>>>>> is using any access attempts will freeze on the client.
>>>> Is that really a NFS4/CTDB question? With hard mounts that's
>>>> pretty much what I would expect.
>>>>
>>>> Volker
>>>>
>>>> --
>>>> SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
>>>> phone: +49-551-370000-0, fax: +49-551-370000-9
>>>> AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
>>>> http://www.sernet.de, mailto:kontakt at sernet.de
>>>>
>>> --
>>> To unsubscribe from this list go to the following URL and read the
>>> instructions:  https://lists.samba.org/mailman/options/samba
>>>
>>>
>>
Hi,

we use pacemaker / corosync for this tasks.

If one node fails fire up the services on the failover node.

No samba clustering involved.

Cheers

Juergen


More information about the samba mailing list