On 03/11/16 14:28, Ralph Böhme wrote:> >> Ah, my smb.conf is missing the "ctdb socket" parameter. According to "man >> smb.conf" this should be set, but I don't remember seeing it on the wiki >> pages. > if it's not set, the default is used which works in many cases, but > not in mine. If the default wasn't working in your setup, you'd > notice, as clients wouldn't be able to talk to ctdb at all. > > -slowI can confirm this made no difference. I see the locking working from windows between the first two servers but *not* the third. This seems to match what I had with smbclient. Again, could it be that an FS that passes ping_pong not be able to work in a CTDB cluster? The developers of my fs (MooseFS) have said that while file flock() is working perfectly there is still no directory flock. Could that be a pointer? Cheers, 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).
Volker Lendecke
2016-Nov-03 19:37 UTC
[Samba] CTDB and locking issues in 4.4.6 (Classic domain)
On Thu, Nov 03, 2016 at 07:11:12PM +0000, Alex Crow via samba wrote:> > > On 03/11/16 14:28, Ralph Böhme wrote: > > > >> Ah, my smb.conf is missing the "ctdb socket" parameter. According to "man > >> smb.conf" this should be set, but I don't remember seeing it on the wiki > >> pages. > > if it's not set, the default is used which works in many cases, but > > not in mine. If the default wasn't working in your setup, you'd > > notice, as clients wouldn't be able to talk to ctdb at all. > > > > -slow > > I can confirm this made no difference. I see the locking working from > windows between the first two servers but *not* the third. This seems to > match what I had with smbclient. Again, could it be that an FS that > passes ping_pong not be able to work in a CTDB cluster? > > The developers of my fs (MooseFS) have said that while file flock() is > working perfectly there is still no directory flock. Could that be a > pointer? >Does your system have consistent inodes and device ids? Does stat /some/shared/file give exactly the same information on all nodes, in particular the Device/Inode fields? Volker
On 03/11/16 19:37, Volker Lendecke wrote:> On Thu, Nov 03, 2016 at 07:11:12PM +0000, Alex Crow via samba wrote: >> >> On 03/11/16 14:28, Ralph Böhme wrote: >>>> Ah, my smb.conf is missing the "ctdb socket" parameter. According to "man >>>> smb.conf" this should be set, but I don't remember seeing it on the wiki >>>> pages. >>> if it's not set, the default is used which works in many cases, but >>> not in mine. If the default wasn't working in your setup, you'd >>> notice, as clients wouldn't be able to talk to ctdb at all. >>> >>> -slow >> I can confirm this made no difference. I see the locking working from >> windows between the first two servers but *not* the third. This seems to >> match what I had with smbclient. Again, could it be that an FS that >> passes ping_pong not be able to work in a CTDB cluster? >> >> The developers of my fs (MooseFS) have said that while file flock() is >> working perfectly there is still no directory flock. Could that be a >> pointer? >> > Does your system have consistent inodes and device ids? Does > > stat /some/shared/file > > give exactly the same information on all nodes, in particular the > Device/Inode fields? > > VolkerThanks Volker, No, it seems it's OK on two servers but not on the third: [root at zalma ~]# stat testfile ... Size: 1286700 Blocks: 2514 IO Block: 65536 regular file Device: 29h/41d Inode: 35820037 Links: 1 Access: (0774/-rwxrwxr--) Uid: ( 3535/ jh3) Gid: ( 513/Domain Users) Access: 2016-11-03 19:51:46.000000000 +0000 Modify: 2016-11-01 13:06:04.000000000 +0000 Change: 2016-11-01 13:06:04.000000000 +0000 Birth: - [root at zalma ~]# ssh zearing "stat testfile" root at zearing's password: ... Size: 1286700 Blocks: 2514 IO Block: 65536 regular file Device: 29h/41d Inode: 35820037 Links: 1 Access: (0774/-rwxrwxr--) Uid: ( 3535/ jh3) Gid: ( 513/Domain Users) Access: 2016-11-03 19:51:46.000000000 +0000 Modify: 2016-11-01 13:06:04.000000000 +0000 Change: 2016-11-01 13:06:04.000000000 +0000 Birth: - [root at zalma ~]# ssh metropolis "stat testfile" root at metropolis's password: ... Size: 1286700 Blocks: 2514 IO Block: 65536 regular file Device: 26h/38d Inode: 35820037 Links: 1 Access: (0774/-rwxrwxr--) Uid: ( 3535/ jh3) Gid: ( 513/Domain Users) Access: 2016-11-03 19:51:46.000000000 +0000 Modify: 2016-11-01 13:06:04.000000000 +0000 Change: 2016-11-01 13:06:04.000000000 +0000 Birth: - NB this is a FUSE mounted FS. What does the Device: XXh/YYd mean? Cheers 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).