[Samba] Winbind process stuck at 100% after changing use_mmap to no

[Alex Crow]

FYI, by "it did, completely" I meant it failed completely.

Even if the only file we have to have on the cluster FS (which now seems 
to be down solely to the ctdb lock file), I'm still worried what these 
failures mean:

1) does the -rw (without -m) test suggest any problems with the MooseFS 
FS I'm serving files to users from?
2) does the mmap test failure mean I should not even have my CTDB lock 
file on MooseFS?
3) Do the inconsistent reports from a ping_pong -rw test show there is a 
major problem with MooseFS as the underlying FS for Samba exports and 
something needs to be done with the underlying FS?

I'm a paying licensee of MooseFS Pro, so I hope you can understand my 
wishes to get this problem sorted. If contracting some of the Sernet 
chaps is required, we've done it before and might be prepared to do so 
in this case.

Best regards

Alex

On 05/07/16 20:12, Alex Crow wrote:
>
>
> On 05/07/16 19:45, Volker Lendecke wrote:
>> On Tue, Jul 05, 2016 at 07:21:16PM +0100, Alex Crow wrote:
>>> I've set up the "DR" side of my cluster to "use mmap = no" and with
>>> "private dir" removed from the smb.conf.
>> Why do you set "use mmap = no"?
>>
>>> I have the MooseFS guys on the case as well. Should I put them in touch
>>> with you or vice/versa?
>> MooseFS should not have any business at all in tdb files. If you still
>> find tdb files used on MooseFS, you should investigate your
>> configuration and modify it such that tdb files only exist on local
>> file systems.
>>
>> Volker
>
> Hi Volker,
>
> There are *no* more tdb files on MooseFS, that's what I'm trying to test.
>
> From the ping_pong wiki page it's instructed to use "use_mmap = no" if 
> the ping_pong test does not work correctly on "ping_ping -m -rw 
> test.file", which it did, completely.
>
> Text here:
>
> "
>
>
>     Testing mmap coherence
>
> If you add the -m switch to ping_pong along with -rw then it will do 
> the I/O coherence test via mmap. It isn't absolutely essential that a 
> cluster filesystem supports coherent mmap for CTDB/Samba, but it's 
> nice for bragging points over other cluster filesystems. If your 
> cluster filesystem doesn't pass this test then just use the "use mmap 
> = no" option in smb.conf. Even if it does pass this test that option 
> may be a good idea on most cluster filesystems."
>
>
> So is this documentation wrong as well? It seems to suggest setting it 
> anyway, which is clearly not working for us (and now for sure there is 
> no involvement with TDB files as I've deleted the "private dir" in 
> smb.conf.
>
>
> The only reason I was asking if you'd like to talk to the MooseFS 
> chaps is because of the failure of the -rw test, which as far as the 
> documentation goes, seems to refer to the shared FS rather than any 
> places where tdb files live.
>
> I hope you can see what I'm getting at here!
>
> Many thanks
>
> Alex
>
>
>


--
This message is intended only for the addressee and may contain
confidential information. Unless you are that person, you may not
disclose its contents or use it in any way and are requested to delete
the message along with any attachments and notify us immediately.
This email is not intended to, nor should it be taken to, constitute advice.
The information provided is correct to our knowledge & belief and must not
be used as a substitute for obtaining tax, regulatory, investment, legal or
any other appropriate advice.

"Transact" is operated by Integrated Financial Arrangements Ltd.
29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300.
(Registered office: as above; Registered in England and Wales under
number: 3727592). Authorised and regulated by the Financial Conduct
Authority (entered on the Financial Services Register; no. 190856).