samba - Jul 2016 - Winbind process stuck at 100% after changing use_mmap to no

On 05/07/16 21:16, Alex Crow wrote:
>
>
> On 05/07/16 21:00, Rowland penny wrote:
>> On 05/07/16 20:49, Alex Crow wrote:
>>> 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.
>>>
>>>
>>
>> ROFL ROFL
>>
>> Do you know who Volker is ???
>>
>> Please listen to him, do what he advises and don't bother
contacting
>> Sernet, because you already have.
>>
>> Rowland
>>
>
> I know who Volker is and I've met Jeremy Allison may years ago at the 
> now defunct London Linux expo..
>
> What am I supposed to be listening to? I'm just suggesting some way I 
> can contribute to MooseFS by getting it to work consistently with 
> Samba/CTDB. Volker suggests just dropping the FS which is not a very 
> good option for our organisation right now. The wiki is unclear and 
> contradictory, and I don't have the facts to update it without risking 
> it being equally broken afterwards, and misleading others, so that's 
> why I'm trying to provide clear information, performing tests, 
> reporting back, and asking for advice to find out how it really *does* 
> work.
>
> I feel a little offended by the tone of this message, as I've been on 
> this list for over 15 years and feel I've helped out a lot of people 
> with other queries I've already experienced.
Sorry if I offended you, but Volker was telling you what you needed to 
do. You were coming over as if you didn't want to do what you were being 
advised to do.
>
> I am prepared to pay Volker via Sernet as this is of great importance 
> to us and will help develop another open source product. Is that so 
> hard to understand?
>
When you put it that way, no, but the way to put it previously, yes.

how should I put this?
MooseFS sounds like it isn't useful with CTDB, you have paid for 
MooseFS, it doesn't work, so you are now blaming Samba. You need to do 
what Volker says and get MooseFS to work with mmap.

Rowland

.
>
> Sorry if I offended you, but Volker was telling you what you needed to
> do. You were coming over as if you didn't want to do what you were
> being advised to do.
No, that is just not the case. I just wanted to be sure of the
implications of what I was doing and what areas of the operation of
Samba and CTDB might be affected given the confusing results of my
ping_pong tests.
>
>>
>> I am prepared to pay Volker via Sernet as this is of great importance
>> to us and will help develop another open source product. Is that so
>> hard to understand?
>>
>
> When you put it that way, no, but the way to put it previously, yes.
I did not "put it" like anything. I just saw an problem in my setup,
read some documents on the samba wiki, followed some advice and saw some
unexpected behaviour. Perhaps I imagined the wiki to be more moderated
that it really is, so my trust was misplaced. I don't blame anyone, all
I'm trying to do is solve a problem.
>
> how should I put this?
> MooseFS sounds like it isn't useful with CTDB, you have paid for
> MooseFS, it doesn't work, so you are now blaming Samba. You need to do
> what Volker says and get MooseFS to work with mmap.
AFAIK I don't need to get it to work with mmap, just get MooseFS to fix
the non-mmap I/O coherence as, as Volker says, mmap is only important
for TDB files and we don't store those on MooseFS.

Again, no "blame" was ever implied. I saw Winbindd using 100% CPU
after
changing the "use mmap" parameter to "no" and was rather
perplexed as to
how that could happen. The first natural place to ask would be this
list, no? I also don't recall using any accusatory or inflammatory
language, just stating observations, posting logs and actually at one or
two points saying I'm also talking to the MooesFS devs.

As a busy sysadmin I rely on a number of sources to design and set up
infrastructure, and sometimes it's easy to get mislead. At no point have
I ever questioned the knowledge of people like Jeremy, Tridge, or
Volker. I'm just dismayed as a professional at getting "ROFLS" in
a
reply to what I feel are perfectly sensible questions stemming from a
misguided source of documentation.

Apologies for clutter.

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).

On Tue, Jul 05, 2016 at 10:12:31PM +0100, Alex Crow
wrote:
> AFAIK I don't need to get it to work with mmap, just get MooseFS to fix
> the non-mmap I/O coherence as, as Volker says, mmap is only important
> for TDB files and we don't store those on MooseFS.
That's correct.

Volker

On Tue, Jul 05, 2016 at 10:12:31PM +0100, Alex Crow
wrote:
> I did not "put it" like anything. I just saw an problem in my
setup,
> read some documents on the samba wiki, followed some advice and saw some
> unexpected behaviour. Perhaps I imagined the wiki to be more moderated
> that it really is, so my trust was misplaced. I don't blame anyone, all
> I'm trying to do is solve a problem.
> 
> >
> > how should I put this?
> > MooseFS sounds like it isn't useful with CTDB, you have paid for
> > MooseFS, it doesn't work, so you are now blaming Samba. You need
to do
> > what Volker says and get MooseFS to work with mmap.
> 
> AFAIK I don't need to get it to work with mmap, just get MooseFS to fix
> the non-mmap I/O coherence as, as Volker says, mmap is only important
> for TDB files and we don't store those on MooseFS.
> 
> Again, no "blame" was ever implied. I saw Winbindd using 100% CPU
after
> changing the "use mmap" parameter to "no" and was
rather perplexed as to
> how that could happen. The first natural place to ask would be this
> list, no? I also don't recall using any accusatory or inflammatory
> language, just stating observations, posting logs and actually at one or
> two points saying I'm also talking to the MooesFS devs.
> 
> As a busy sysadmin I rely on a number of sources to design and set up
> infrastructure, and sometimes it's easy to get mislead. At no point
have
> I ever questioned the knowledge of people like Jeremy, Tridge, or
> Volker. I'm just dismayed as a professional at getting
"ROFLS" in a
> reply to what I feel are perfectly sensible questions stemming from a
> misguided source of documentation.
Sorry for that Alex. Rowland, please be nicer to professional
people just asking for help.

I'm just back from a weeks vacation and trying to catch up.

What is the current state of your problem Alex ? As I understand
it you are requesting the MooseFS developers fix the mmap/pwrite
coherence issues.

Is there anything else you need from Samba ? What issues are
outstanding for you ?

Cheers,

	Jeremy.