[Samba] Samba CTDB with data coming via pNFS?
Greetings, Does anyone know whether I'll encounter problems serving out CIFS using Samba/CTDB where the servers are pNFS clients? Specifically I'm thinking that I'll have a number of RHEL 6.2 boxes connecting to netapp storage using pNFS. These boxes will then serve a variety of CIFS clients. JR -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba CTDB with data coming via pNFS?
Greetings all, Does anyone know whether I'll encounter problems serving out CIFS using Samba/CTDB where the servers are pNFS clients? In more detail: The servers are linux virtual machines running RHEL 6.2. They mount volumes coming from the latest net app OS (which runs a pNFS service). I'll then put samba and CTDB on of these machines to serve data to our windows clients. Samba will authenticate to a windows AD. I'm not yet sure how the authentication/acls will work. I've run a similar configuration using GPFS as the backend filesystem (fast for sequentail IO but challenged with metadata performance). Will locking be an issue? Thanks for any insight, JR -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba/ctdb on AIX 6.1
I'm trying to test Samba 3.5.8 with ctdb on AIX 6.1 and running into some issues. I was able to get the latest ctdb code built with some small changes and then get a working cluster, but without CTDB managing the public IP addresses or Samba startup/shutdown. The included event script for managing interfaces is linux specific. Is it possible to allow ctdb to manage the public cluster IP addresses if I re-write the necessary scripts to work on AIX. Even better, is there anyone who has already done this work and can share it? Thanks, John Janosik jpjan...@us.ibm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba ctdb clustering with ldap backend?
On Wed, Apr 6, 2011 at 2:10 AM, Daniel Müller muel...@tropenklinik.de wrote: My both ldap server run in multi master replication mode. So I think everything should be the same on both servers all the time? So it could work anyway? No, you run the risk of collisions, because of the replication delay between servers. You need something fully synchronous, unless you're going to take care of conflicts yourself, including any files that might have been created on different nodes with the same uid by different SIDs. --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: jmcdo...@gmail.com [mailto:jmcdo...@gmail.com] Im Auftrag von Jim McDonough Gesendet: Dienstag, 5. April 2011 19:01 An: muel...@tropenklinik.de Cc: samba@lists.samba.org Betreff: Re: [Samba] samba ctdb clustering with ldap backend? On Tue, Apr 5, 2011 at 3:35 AM, Daniel Müller muel...@tropenklinik.de wrote: I have two samba servers auth agains ldap, so I use: idmap backend = ldap:ldap://127.0.0.1 Is it possible to setup ctdb to run with a ldap backend? I don't see why not. The point of tdb2 was to not get different uids/gids on different nodes. However, you'd need to have only one ldap server that they all use. Your current setup would not work. I know ctdb uses: idmap backend = tdb2 -- Jim McDonough Samba Team SUSE labs jmcd at samba dot org jmcd at themcdonoughs dot org -- Jim McDonough Samba Team SUSE labs jmcd at samba dot org jmcd at themcdonoughs dot org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba ctdb clustering with ldap backend?
My both ldap server run in multi master replication mode. So I think everything should be the same on both servers all the time? So it could work anyway? --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: jmcdo...@gmail.com [mailto:jmcdo...@gmail.com] Im Auftrag von Jim McDonough Gesendet: Dienstag, 5. April 2011 19:01 An: muel...@tropenklinik.de Cc: samba@lists.samba.org Betreff: Re: [Samba] samba ctdb clustering with ldap backend? On Tue, Apr 5, 2011 at 3:35 AM, Daniel Müller muel...@tropenklinik.de wrote: I have two samba servers auth agains ldap, so I use: idmap backend = ldap:ldap://127.0.0.1 Is it possible to setup ctdb to run with a ldap backend? I don't see why not. The point of tdb2 was to not get different uids/gids on different nodes. However, you'd need to have only one ldap server that they all use. Your current setup would not work. I know ctdb uses: idmap backend = tdb2 -- Jim McDonough Samba Team SUSE labs jmcd at samba dot org jmcd at themcdonoughs dot org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba ctdb clustering with ldap backend?
Dear all, I have two samba servers auth agains ldap, so I use: idmap backend = ldap:ldap://127.0.0.1 Is it possible to setup ctdb to run with a ldap backend? I know ctdb uses: idmap backend = tdb2 Any suggestions? Greetings Daniel --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba ctdb clustering with ldap backend?
On Tue, Apr 5, 2011 at 3:35 AM, Daniel Müller muel...@tropenklinik.de wrote: I have two samba servers auth agains ldap, so I use: idmap backend = ldap:ldap://127.0.0.1 Is it possible to setup ctdb to run with a ldap backend? I don't see why not. The point of tdb2 was to not get different uids/gids on different nodes. However, you'd need to have only one ldap server that they all use. Your current setup would not work. I know ctdb uses: idmap backend = tdb2 -- Jim McDonough Samba Team SUSE labs jmcd at samba dot org jmcd at themcdonoughs dot org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] SAMBA + CTDB
Hello, I am currently trying to compile newest samba 3.5.3 with ctdb (from git repository) on Debian Lenny (version 5.0.4). I am using following 'configure' command: ./configure --with-cluster-support --with-shared-modules=idmap_tdb2 --with-ads --enable-pie=no and unfortunatelly I have following error: checking for ctdb.h... no checking for ctdb_private.h... no checking for CTDB_CONTROL_TRANS3_COMMIT declaration... yes checking for struct ctdb_tcp_client... no checking for struct ctdb_control_tcp... yes checking for struct ctdb_control_tcp_addr... yes checking cluster support... configure: error: ctdb_private.h is required for cluster support In config.log I can see: configure:73944: checking for ctdb.h configure:73975: gcc -c -O -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -I./../lib/popt -I/usr/include -DLDAP_DEPRECATED -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -I./../lib/popt -I./../lib/talloc -I../lib/tdb/include conftest.c 5 In file included from conftest.c:602: /usr/local/include/ctdb.h:180: error: stray '#' in program /usr/local/include/ctdb.h:180: error: expected ';', ',' or ')' before '__USED_RESERVED_WORD_private__' /usr/local/include/ctdb.h:208: error: expected declaration specifiers or '...' before 'ctdb_callback_t' /usr/local/include/ctdb.h:250: error: stray '#' in program /usr/local/include/ctdb.h:250: error: expected ';', ',' or ')' before '__USED_RESERVED_WORD_private__' /usr/local/include/ctdb.h:267: error: expected declaration specifiers or '...' before 'ctdb_rrl_callback_t' /usr/local/include/ctdb.h:313: error: expected declaration specifiers or '...' before 'ctdb_callback_t' /usr/local/include/ctdb.h:339: error: expected declaration specifiers or '...' before 'ctdb_callback_t' /usr/local/include/ctdb.h:385: error: expected declaration specifiers or '...' before 'ctdb_callback_t' /usr/local/include/ctdb.h:413: error: expected declaration specifiers or '...' before 'ctdb_callback_t' Any tips? Please let me know if more details is needed. Thanks! Best regards -- View this message in context: http://old.nabble.com/SAMBA-%2B-CTDB-tp28953026p28953026.html Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba ctdb doesn't set default gateway properly on second node;
Adding samba technical list to get some help here... -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of Hammitt, Charles Allen Sent: Wednesday, February 10, 2010 2:36 PM To: samba@lists.samba.org Subject: Re: [Samba] samba ctdb doesn't set default gateway properly on second node; I guess that would need to be a service ctdb restart Is that even a very good idea to do? I put an ip route add command in the rc.local file already. And it doesn't seem to help. Of course, /etc/sysconfig/network is set properly as well. If I run the ip route add command on the command line, then the problem there is for some reason it adds an H flag for the routing table information which can be seen from netstat -rn. The problem with the H flag is that it only seems to allow local access to that interface (like 127.0.0.1 loopback) and not other host nodes...which is the problem in the first place. Also, this won't address link down issues; only will ensure that the interface route and default gateway info is correct upon system reboot. From: Sent: Wednesday, February 10, 2010 2:16 PM To: Hammitt, Charles Allen Subject: RE: samba ctdb doesn't set default gateway properly on second node; Without looking into it further My first thought is to put a correction item in the /etc/rc.local. This is the last thing execute during the reboot. From: Hammitt, Charles Allen Sent: Wednesday, February 10, 2010 2:08 PM To: samba@lists.samba.org Subject: samba ctdb doesn't set default gateway properly on second node; Hey all, I am trying to figure out a weird problem. I have a two node ctdb samba setup where the first node acts as expected setting the default gateway (startup shutdown takeip recoveryip) if there is a network blip / link down, but the second node does not set the default gateway properly on the initial recovery of the link after the blip has occurred. If I restart the machine or restart the ctdb service, then it does come back with the proper gateway and traffic flows as expected. Problem is I wouldn't think I need to do a restart or reboot to get the interface default gateway/route to be reset. Note that the interface address itself is set, but routing is the problem. Any thoughts here? I was going to send off this message yesterday but I started poking around in the event.d directory looking around for something that might help. I was reading the README file there and this note struck me as kind of odd: Each NN must be unique and duplicates will cause undefined behaviour. I.e. having both 10.interfaces and 10.otherstuff is not allowed. I say this is odd as I have three 11's which were put in on the default install: -rwxr-xr-x 1 root root 2178 Jun 29 2009 11.natgw -rwxr-xr-x 1 root root 340 Jul 17 2009 11.route -rwxr-xr-x 1 root root 798 Jun 29 2009 11.routing So either the note is wrong, or perhaps it is part of my bug. In addition, I read in the 11.route file the comment about adding a static-routes file. I had not previously had this file so I thought, this is surely the cause of my problems. But no...sadly it is not. I had another outage today because the gateway or route was not set when the link came back up. Again, any thoughts? Noting that the only thing I do to get the interfaces to work as expected is to restart the ctdb service. Interestingly enough, the first node of the cluster which is the exact same config never shows this particular problem. Moreover, the static-routes note is not in the documentation and it probably should be put there. The only place I found out about the static-routes were by reading the 11.route file itself. So it might be legacy and not even needed or used nowadays...idk. rpm -qa|grep ctdb ctdb-1.0.86-1 uname -a Linux 2.6.18-128.7.1.el5 #1 SMP Wed Aug 19 04:00:49 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba ctdb doesn't set default gateway properly on second node;
I guess that would need to be a service ctdb restart Is that even a very good idea to do? I put an ip route add command in the rc.local file already. And it doesn't seem to help. Of course, /etc/sysconfig/network is set properly as well. If I run the ip route add command on the command line, then the problem there is for some reason it adds an H flag for the routing table information which can be seen from netstat -rn. The problem with the H flag is that it only seems to allow local access to that interface (like 127.0.0.1 loopback) and not other host nodes...which is the problem in the first place. Also, this won't address link down issues; only will ensure that the interface route and default gateway info is correct upon system reboot. From: Sent: Wednesday, February 10, 2010 2:16 PM To: Hammitt, Charles Allen Subject: RE: samba ctdb doesn't set default gateway properly on second node; Without looking into it further My first thought is to put a correction item in the /etc/rc.local. This is the last thing execute during the reboot. From: Hammitt, Charles Allen Sent: Wednesday, February 10, 2010 2:08 PM To: samba@lists.samba.org Subject: samba ctdb doesn't set default gateway properly on second node; Hey all, I am trying to figure out a weird problem. I have a two node ctdb samba setup where the first node acts as expected setting the default gateway (startup shutdown takeip recoveryip) if there is a network blip / link down, but the second node does not set the default gateway properly on the initial recovery of the link after the blip has occurred. If I restart the machine or restart the ctdb service, then it does come back with the proper gateway and traffic flows as expected. Problem is I wouldn't think I need to do a restart or reboot to get the interface default gateway/route to be reset. Note that the interface address itself is set, but routing is the problem. Any thoughts here? I was going to send off this message yesterday but I started poking around in the event.d directory looking around for something that might help. I was reading the README file there and this note struck me as kind of odd: Each NN must be unique and duplicates will cause undefined behaviour. I.e. having both 10.interfaces and 10.otherstuff is not allowed. I say this is odd as I have three 11's which were put in on the default install: -rwxr-xr-x 1 root root 2178 Jun 29 2009 11.natgw -rwxr-xr-x 1 root root 340 Jul 17 2009 11.route -rwxr-xr-x 1 root root 798 Jun 29 2009 11.routing So either the note is wrong, or perhaps it is part of my bug. In addition, I read in the 11.route file the comment about adding a static-routes file. I had not previously had this file so I thought, this is surely the cause of my problems. But no...sadly it is not. I had another outage today because the gateway or route was not set when the link came back up. Again, any thoughts? Noting that the only thing I do to get the interfaces to work as expected is to restart the ctdb service. Interestingly enough, the first node of the cluster which is the exact same config never shows this particular problem. Moreover, the static-routes note is not in the documentation and it probably should be put there. The only place I found out about the static-routes were by reading the 11.route file itself. So it might be legacy and not even needed or used nowadays...idk. rpm -qa|grep ctdb ctdb-1.0.86-1 uname -a Linux 2.6.18-128.7.1.el5 #1 SMP Wed Aug 19 04:00:49 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba ctdb doesn't set default gateway properly on second node;
Hey all, I am trying to figure out a weird problem. I have a two node ctdb samba setup where the first node acts as expected setting the default gateway (startup shutdown takeip recoveryip) if there is a network blip / link down, but the second node does not set the default gateway properly on the initial recovery of the link after the blip has occurred. If I restart the machine or restart the ctdb service, then it does come back with the proper gateway and traffic flows as expected. Problem is I wouldn't think I need to do a restart or reboot to get the interface default gateway/route to be reset. Note that the interface address itself is set, but routing is the problem. Any thoughts here? I was going to send off this message yesterday but I started poking around in the event.d directory looking around for something that might help. I was reading the README file there and this note struck me as kind of odd: Each NN must be unique and duplicates will cause undefined behaviour. I.e. having both 10.interfaces and 10.otherstuff is not allowed. I say this is odd as I have three 11's which were put in on the default install: -rwxr-xr-x 1 root root 2178 Jun 29 2009 11.natgw -rwxr-xr-x 1 root root 340 Jul 17 2009 11.route -rwxr-xr-x 1 root root 798 Jun 29 2009 11.routing So either the note is wrong, or perhaps it is part of my bug. In addition, I read in the 11.route file the comment about adding a static-routes file. I had not previously had this file so I thought, this is surely the cause of my problems. But no...sadly it is not. I had another outage today because the gateway or route was not set when the link came back up. Again, any thoughts? Noting that the only thing I do to get the interfaces to work as expected is to restart the ctdb service. Interestingly enough, the first node of the cluster which is the exact same config never shows this particular problem. Moreover, the static-routes note is not in the documentation and it probably should be put there. The only place I found out about the static-routes were by reading the 11.route file itself. So it might be legacy and not even needed or used nowadays...idk. rpm -qa|grep ctdb ctdb-1.0.86-1 uname -a Linux 2.6.18-128.7.1.el5 #1 SMP Wed Aug 19 04:00:49 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
