[Samba] Samba share over a NFS mount (tuning)
Hi, I have a server that run OpenSuse 10.3, this server run VMware Server and host an OpenSuse 10.3 virtual machine witch is a Samba file server for my windows clients. The goal behind having a OpenSuse hosting an OpenSuse virtual machine is to separate the configurations from the data so I can easily change the configurations without affecting the data. The host keep all the data and share it with the virtual machine with NFS v3, so the virtual machine mount the NFS share and then a use Samba 3.0.26a to share the NFS mounted folder for my windows clients. The network I use between my host and my virtual machine is an Host-only virtual network. My virtual machine use a bridged network over a dedicated 1Gb Ethernet card to communicate with the windows clients. I reuse a smb.conf from the previous Samba (3.0.25b) file server witch was functioning with absolutely no problems. The problem I have with my new Samba file server is that my Vista client have a 20 to 60 second delay when they open a MS Office 2007 file. They have the same delay with MS Office 2003 and all the Office's file the Vista clients open with MS Office 2003 are read only. I think it is a file lock issue because went I disable the file lock at the NFS mount or in Samba smb.conf file. In my case, I just cannot disable file lock in my production environment. Thanks for your help, Mathieu Beaudoin Responsable des T.I. CVT Corp Technologies de vitesse variable Variable Speed Technologies -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] WinXP Pro can't join Domain (Samba PDC) after server migration but current domain machine are OK
Hi, I had a Samba PDC running on unstable hardware. I migrate everything on a new machine, I transferred all the configuration files (smb.conf, smbpasswd, .), transferred all the users and groups. Everything was working 100% until I had to join a new machine to Domain, WinXP Pro SP2 can't find de Domin Controler, but all the WinXP Pro SP2 that where already in the Domain before the migration can logon fine, their roaming profiles are updated fine and they access the shares with no problems. I just can't join a new machine. I reinstall Samba completely on the server, reconfigure everything manually (not using the old smb.conf) and no change. I try to disable the firewall, no change. I'm out of idea. I run samba 3.0.26 on Opensuse 10.3 (same as the old server). [global] workgroup = SOE-DOMAIN server string = PDC - File Server log file = /data/log/samba_log.txt deadtime = 15 printcap name = cups add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ logon path = \\%L\profiles\.msprofile logon drive = P: logon home = \\%L\%U\.9xprofile domain logons = Yes preferred master = Yes domain master = Yes wins proxy = Yes wins support = Yes ldap ssl = no usershare allow guests = Yes acl group control = Yes profile acls = Yes map acl inherit = Yes printing = cups cups options = raw print command = lpq command = %p lprm command = store dos attributes = Yes strict locking = Yes include = /etc/samba/dhcp.conf [profiles] comment = Network Profiles Service path = %H read only = No create mask = 0600 directory mask = 0700 browseable = No [users] comment = All users path = /home read only = No inherit acls = Yes veto files = /aquota.user/groups/shares/ browseable = No [groups] comment = All groups path = /home/groups read only = No inherit acls = Yes browseable = No [printers] comment = All Printers path = /var/tmp create mask = 0600 printable = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin, root force group = ntadmin create mask = 0664 directory mask = 0775 [data] comment = data path = /data/data read only = No inherit permissions = Yes inherit acls = Yes inherit owner = Yes [programme] comment = Network Profiles Service path = %H read only = No create mask = 0600 directory mask = 0700 use sendfile = Yes browseable = No [email] path = /data/email/ read only = No inherit permissions = Yes inherit acls = Yes inherit owner = Yes case sensitive = No browseable = No blocking locks = No locking = No oplocks = No posix locking = No strict locking = No msdfs proxy = no Thanks for your help and let me know if you need more infos, Mathieu Beaudoin Responsable des T.I. CVT Corp Technologies de vitesse variable Variable Speed Technologies -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] WinXP Pro can't join Domain (Samba PDC) after server migration but current domain machine are OK
Hi Rubin, Thanks for your quick answer. I use "pdbedit -i tdbsam -e smbpasswd" and "pdbedit -i smbpasswd -e tdbsam" and I'm still having the same problems. Did I forgot something or didn't do the right thing? Thanks, Mathieu Beaudoin Responsable des T.I. CVT Corp Technologies de vitesse variable Variable Speed Technologies -Message d'origine- De : Rubin Bennett [mailto:[EMAIL PROTECTED] Envoyé : 13 mars 2008 21:33 À : Mathieu Beaudoin Cc : samba@lists.samba.org Objet : Re: [Samba] WinXP Pro can't join Domain (Samba PDC) after server migration but current domain machine are OK On Thu, 2008-03-13 at 20:10 -0400, Mathieu Beaudoin wrote: > Hi, > > I had a Samba PDC running on unstable hardware. I migrate everything on a > new machine, I transferred all the configuration files (smb.conf, smbpasswd, > .), transferred all the users and groups. Everything was working 100% until > I had to join a new machine to Domain, WinXP Pro SP2 can't find de Domin > Controler, but all the WinXP Pro SP2 that where already in the Domain before > the migration can logon fine, their roaming profiles are updated fine and > they access the shares with no problems. I just can't join a new machine. I > reinstall Samba completely on the server, reconfigure everything manually > (not using the old smb.conf) and no change. I try to disable the firewall, > no change. I'm out of idea. > I've seen similar behaviour before, always after an upgrade (it seems more common when upgrading a 32bit OS to a 64 bit, IIRC). My fix was to export the tdb to smbpasswd, and reimport. That seems to fix it pretty consistently. Rubin > > > I run samba 3.0.26 on Opensuse 10.3 (same as the old server). > > > > > > [global] > > workgroup = SOE-DOMAIN > > server string = PDC - File Server > > log file = /data/log/samba_log.txt > > deadtime = 15 > > printcap name = cups > > add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody > -s /bin/false %m$ > > logon path = \\%L\profiles\.msprofile > > logon drive = P: > > logon home = \\%L\%U\.9xprofile > > domain logons = Yes > > preferred master = Yes > > domain master = Yes > > wins proxy = Yes > > wins support = Yes > > ldap ssl = no > > usershare allow guests = Yes > > acl group control = Yes > > profile acls = Yes > > map acl inherit = Yes > > printing = cups > > cups options = raw > > print command = > > lpq command = %p > > lprm command = > > store dos attributes = Yes > > strict locking = Yes > > include = /etc/samba/dhcp.conf > > > > [profiles] > > comment = Network Profiles Service > > path = %H > > read only = No > > create mask = 0600 > > directory mask = 0700 > > browseable = No > > > > [users] > > comment = All users > > path = /home > > read only = No > > inherit acls = Yes > > veto files = /aquota.user/groups/shares/ > > browseable = No > > > > [groups] > > comment = All groups > > path = /home/groups > > read only = No > > inherit acls = Yes > > browseable = No > > > > [printers] > > comment = All Printers > > path = /var/tmp > > create mask = 0600 > > printable = Yes > > browseable = No > > > > [print$] > > comment = Printer Drivers > > path = /var/lib/samba/drivers > > write list = @ntadmin, root > > force group = ntadmin > > create mask = 0664 > > directory mask = 0775 > > > > [data] > > comment = data > > path = /data/data > > read only = No > > inherit permissions = Yes > > inherit acls = Yes > > inherit owner = Yes > > > > [programme] > > comment = Network Profiles Service > > path = %H > > read only = No > > create mask = 0600 > > directory mask = 0700 > > use sendfile = Yes > > browseable = No > > > > [email] > > path = /data/email/ > > read only = No > > inherit permissions = Yes > > inherit acls = Yes > > inherit owner = Yes > > case sensitive = No &g
[Samba] Can't kill smbd process
Hi, Since this week my Samba keep accumulating smbd process that keep lock on files and neither me as root or samba itself can't kill. The only way to release the locked files is to reboot the machine and this is really annoying for all the clients. I read in a forum that this might be link with a kernel corruption, but this threads hasn't been active in a long time and wasn't so clear about the corruption. So I turn on your experiences and knowledge to help me find a solution to this problem. I run Samba 3.0.26a-3.5 on Opensuse 10.3 with the 2.6.22.17-0.1-default. I don't thing the problem come from my smb.conf, the deadtime is set to 10 minutes but since those process keep a lock on files they are not kill after 10 minutes of inactivity. [global] workgroup = Bidon server string = PDC - File Server log file = /log/samba.log server signing = auto deadtime = 10 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = cups add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ logon path = \\%L\profiles\.msprofile logon drive = P: logon home = \\%L\%U\.9xprofile domain logons = Yes preferred master = Yes domain master = Yes wins proxy = Yes wins server = eth0:10.0.0.11 wins support = Yes ldap ssl = no acl group control = Yes profile acls = Yes map acl inherit = Yes printing = cups cups options = raw print command = lpq command = %p lprm command = store dos attributes = Yes strict locking = Yes include = /etc/samba/dhcp.conf [data] comment = data path = /data/data read only = No inherit permissions = Yes inherit acls = Yes inherit owner = Yes use sendfile = Yes dos filemode = Yes dos filetime resolution = Yes [email] path = /data/email/ read only = No browseable = No blocking locks = No locking = No oplocks = No level2 oplocks = No posix locking = No strict locking = No dos filemode = Yes dos filetime resolution = Yes Thank you, Mathieu Beaudoin Responsable des T.I. CVT Corp Technologies de vitesse variable Variable Speed Technologies -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Can't kill smbd process
Hi, Sorry for not responding in a long time, I been really busy these days. To kill the process, I use "kill -9 " as root and it do nothing, no error message and the process still run. I found the possible source of this problem : each night we have a backup server (running opensuse 10.3) that connect to the file server (mount -t cifs ...) copy the files on his own hard drive, umount the share and then start transferring the files on tapes. When I check the swat status page in the morning and "ps aux | greo smbd", I got like 20 process or more coming for the backup server file transfer and all those process can't be kill by "sudo kill -9 pid". From this point some smbd process, that are created by normal user use, can't die either and keeps lock on files. One night, I shutdown the backup server and the next day every thing was working normally, no unkillable process. Thank you, Mathieu Beaudoin Responsable des T.I. CVT Corp Technologies de vitesse variable Variable Speed Technologies -Message d'origine- De : James A. Dinkel [mailto:[EMAIL PROTECTED] Envoyé : 21 avril 2008 11:43 À : samba@lists.samba.org Objet : RE: [Samba] Can't kill smbd process TCP_NODELAY is still usefull and has a noticeable improvement in responsiveness. SO_RCVBUF=8192 and SO_SNDBUF=8192 are outdated and actually make things worse if running with a 2.6 kernel (they do help if running on a 2.4 kernel). But I too, am sure changing these will not fix your problem (but probably will improve network performance). How are you killing the open files? With "kill -9"? I kill locked, open files by finding the pid with lsof and then close it with "sudo kill -9 pidnumber". I've never had kill -9 fail me and I imagine you would have to have serious kernel problems if kill -9 failed to kill a pid.3 James -Original Message From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Novosielski Sent: Friday, April 18, 2008 3:55 PM To: samba@lists.samba.org Subject: Re: [Samba] Can't kill smbd process I've seen written here many times that the TCP options are old/no longer needed. Not that I expect that removing them will fix anything. Seems to me you have an awful lot things defined specifically there. I don't know how those relate to the defaults. Or is that testparm -v output? - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFICQqrmb+gadEcsb4RAmjxAKCQudeurwtv7YWf20mPvr/5pTVUqACfbF+z bTXN5/lgADDY5qywZKJEzp0= =IXls -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Can I mount an NFS volume and re-export via SAMBA?
By my experience, it is possible but I had to turn off this setup because we had issues with MS Office files. The oplock wasn't working correctly and we had problems with saving MS Excel files on this share. It was also not easy to tune the performance, the samba share had a tendency to lag when we where browsing it or when we where opening files. Mathieu Beaudoin -Message d'origine- De : Jim Hall [mailto:[EMAIL PROTECTED] Envoyé : 5 mai 2008 12:23 À : samba@lists.samba.org Objet : [Samba] Can I mount an NFS volume and re-export via SAMBA? We have an NFS filer right now that we need to provide our windows users access too. For various reasons they won't use SFU, etc. In our legacy environment we have a file server that does NFS/CIFS natively. In our new environment not so much. We want to provide this service to our users and the solution proposed to me is to utilize SAMBA as the mechanism to do so. After doing exhaustive googling and searching I can't seem to find if this is doable, and if it is what kind of things I should be on the lookout for, or configuring the system for. So first, is it possible? Second, if it is possible is it just a matter of mounting the NFS volume on the SAMBA server and then re-exporting to the Windows clients? Thanks, Jim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
