Re: [Samba] Samba file share slowdown
The thought was that the dos workstations would be unhappy with ntfs. I may well have been wrong there. I found the key bit. For a share with multiple stations sharing dbf files using CA clipper 5.2 as the program language, optlocks need to be off. The part about clipper and dbf files may not be a specific part of my problem, multiple stations attempting to share read/write acess certainly is. We have half a dozen or so dbf files that are heavily shared between perhaps 30 workstations. Setting oplocks off made a huge difference. The online help seems to suggest the opposite-- that oplocks would be a positive influence on multiple access useage, the chapter in the docs that I finally found that explains it wasn't easy to find. I didn't find it till someone else suggested this fix. When I searched with that question in mind I found it. Thanks for your help, overall samba is a very good thing. Jim Hurlburt Yakima, WA On 3/11/11, Jeremy Allison wrote: > On Tue, Mar 08, 2011 at 10:41:19AM -0800, James Hurlburt wrote: >> Jeremy: >> Looks like I may have made a mistake attaching the file. >> Here is my smb.conf in the email. >> >> If both trys actually worked, please ignore one. > > The only strange thing I can see is: > > fstype = FAT > > in your share definitions. Why are you setting that ? > > Jeremy. > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba file share slowdown
Jeremy: Looks like I may have made a mistake attaching the file. Here is my smb.conf in the email. If both trys actually worked, please ignore one. Jim # Samba config file created using SWAT # from UNKNOWN (10.23.0.118) # Date: 2011/03/07 12:24:08 [global] workgroup = ATRIUM-DW server string = %h server (Samba, Ubuntu) map to guest = Bad User obey pam restrictions = Yes pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . unix password sync = Yes lanman auth = Yes syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 deadtime = 15 dns proxy = No default service = global usershare allow guests = Yes panic action = /usr/share/samba/panic-action %d [printers] comment = All Printers path = /var/spool/samba create mask = 0700 printable = Yes browseable = No browsable = No [print$] comment = All Printers path = /var/spool/samba valid users = @users admin users = @admin read only = No create mask = 0700 guest ok = Yes browseable = No browsable = No [bestbilt] path = /atrium/bestbilt valid users = @users admin users = @admin force group = users read only = No create mask = 0664 force create mode = 0664 directory mask = 0775 force directory mode = 0775 strict locking = No fstype = FAT [vol1] path = /atrium/vol1 valid users = @users admin users = @admin force group = users read only = No create mask = 0664 force create mode = 0664 directory mask = 0775 force directory mode = 0775 fstype = FAT [programs] path = /atrium/programs valid users = @users admin users = @admin force group = users read only = No create mask = 0664 force create mode = 0664 directory mask = 0775 force directory mode = 0775 fstype = FAT [testjim] path = /atrium/testjim valid users = @computer admin users = @admin force group = computer read only = No create mask = 0664 force create mode = 0664 directory mask = 0775 force directory mode = 0775 [accounting] path = /atrium/accounting valid users = @accounting admin users = @admin force group = accounting read only = No create mask = 0660 force create mode = 0660 directory mask = 0770 force directory mode = 0770 [homes] comment = home directories valid users = %S admin users = @admin read only = No browseable = No browsable = No fstype = FAT [computer] path = /atrium/secure/COMPUTER valid users = @computer admin users = @admin force group = computer read only = No create mask = 0660 force create mode = 0660 directory mask = 0770 force directory mode = 0770 [testprinter2] printable = Yes -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba] file share slowdown
Jeremy: Attached is the working smb.conf, created with swat. Thanks for your attention, Jim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] file share slowdown
Sirs: We are a Vinyl window manufacturing plant in central Washington State, USA. We have been running linux with samba for file and print services for eight or ten years now. Much of our production software is in house, and built on CA clipper 5.2, using dbf files as the primary data store. The clipper dbf file format supports both record locking and file locking along with shared file access. This worked very well on Novell netware and was working ok on samba 3.0.23. We had a samba server running for several years. I believe it was 6.06 with samba 3.0.23 although I'm no longer certain of either of those two versions. We have about six stations running dos 6.22 and four running windows 98. They are part of production machines, and changing the operating system is not an option. I had managed to tweak the samba config file so that file sharing wasn't a big problem, the system was responsive and running fairly smoothly. We have numerous clients running winXP with no obvious problems. We are, and have been running the Samba server with User validation. We are part of a windows domain, but haven't figured out a way to have the dos machines login as domain members. The xp stations use the domain for authentication, then we maintain a parallel set of logins on the linux box and samba file server. Again, this was working OK, pre crash. A month or so ago, we lost two hard drives on the file server and had to do a rebuild. I had tried to update the samba version a time or two in the interem and failed. I couldn't get the dos machines to connect to samba and access the necessary data files. One gentleman on the samba list said that this was a problem with lanman protocol, and aparently fixed it. Samba 3.4.7 allows logins file access without any problems. The current problem is that shared clipper files are very slow. It appears as if record locking instead of file locking isn't being recognized by Samba. When production is going, 20 second delays for file access are common. This was not true six weeks ago before the server crash. I have studied on the smb.conf file at great length, trying several variations without sucess. Any advice or hints of what to study now would be most welcome, Jim Hurlburt Atrium Windows and Doors Northwest. Yakima, WA USA The global portion plus the mains share of the smb.conf file in verbose mode. *** # Samba config file created using SWAT # from UNKNOWN (10.23.0.118) # Date: 2011/03/07 15:23:58 [global] dos charset = CP850 unix charset = UTF-8 display charset = LOCALE workgroup = ATRIUM-DW realm = netbios name = BBI-SAM-1-SRV netbios aliases = netbios scope = server string = %h server (Samba, Ubuntu) interfaces = bind interfaces only = No security = USER auth methods = encrypt passwords = Yes update encrypted = No client schannel = Auto server schannel = Auto allow trusted domains = Yes map to guest = Bad User null passwords = No obey pam restrictions = Yes password server = * smb passwd file = /etc/samba/smbpasswd private dir = /etc/samba passdb backend = tdbsam algorithmic rid base = 1000 root directory = guest account = nobody enable privileges = Yes pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . passwd chat debug = No passwd chat timeout = 2 check password script = username map = password level = 0 username level = 0 unix password sync = Yes restrict anonymous = 0 lanman auth = Yes ntlm auth = Yes client NTLMv2 auth = No client lanman auth = No client plaintext auth = No preload modules = dedicated keytab file = kerberos method = default map untrusted to domain = No log level = 0 syslog = 0 syslog only = No log file = /var/log/samba/log.%m max log size = 1000 debug timestamp = Yes debug prefix timestamp = No debug hires timestamp = No debug pid = No debug uid = No debug class = No enable core files = Yes smb ports = 445 139 large readwrite = Yes max protocol = NT1 min protocol = CORE min receivefile size = 0 read raw = Yes write raw = Yes disable netbios = No reset on zero vc = No acl compatibility = auto defer sharing violations = Yes nt pipe support = Yes nt status support = Yes announce version = 4.9 announce as = NT max mux = 50 max xmit = 16644 name res
[Samba] (no subject)
Sirs: I have a Ubuntu 6.06 samba 3.0.22 file server running on linux. I am attempting to update the file server to ubuntu 8.10, samba 3.2.3. I have been attempting this, intermittently, for some time which is why 8.10. I have 10 MSDOS (mostly 6.22) workstations as a part of the network. The ones that have to run, control production machinery on the plant floor. Updating the operating system on those machines is effectivly impossible. There are some of them that run software that I control, most of them use vendor supplied software to control the older machines. They are using lanman 2.2 as the client software. (I have many xp workstations, they work fine with both systems. I can map drives, read and save and run the same dos exe files that the dos stations are failing on. Print stuff...) On the old server, the dos stations can log in and use network resources. Thus far, I have failed to make them work on the new server. The relevant parts of the smb.conf files for the servers are -- The 3.0.22 server. This one is the production server and the dos stations work. # Samba config file created using SWAT # from 10.23.0.118 (10.23.0.118) # Date: 2010/01/29 09:46:06 [global] workgroup = ATRIUM-DW server string = Samba passwd program = /usr/bin/passwd %u unix password sync = Yes change notify timeout = 30 deadtime = 30 printcap name = CUPS disable spoolss = Yes show add printer wizard = No ldap ssl = no case sensitive = No [bestbilt] comment = Mapped as U: path = /atrium/bestbilt valid users = @users force group = users read only = No create mask = 0664 force create mode = 0664 directory mask = 0775 force directory mode = 0775 oplocks = No level2 oplocks = No strict locking = No *** The 3.2.3 server # Samba config file created using SWAT # from UNKNOWN () # Date: 2010/02/02 13:20:51 [global] workgroup = ATRIUM-DW guest account = bbijimhur lanman auth = Yes ldap ssl = no [bestbilt] comment = working production data path = /atrium/bestbilt username = bbijimhur valid users = @users force group = users read only = No guest ok = Yes [dosbbilt] comment = win94 for dos workstations path = /atrium/bestbilt read only = No guest ok = Yes This smb.conf file is the best one I have been able to create for the dos stations. With it, I can log in and map the drive. net use u: \\bbi-sam-2-srv\bestbilt I can do directory listings and change directory to u:\win94 When I attempt to run a dos program (tracking.exe) I get the following u:\win94\> Tracking NET805: NETWORK DEVICE NO LONGER EXISTS READING DRIVE U Abort, Retry, Fail? f Access denied. I have much the same error if I put the executable on the local drive and attempt to use shared .dbf data files from the server. I can connect to the old server with the same box. It takes a few minutes to change all the config files for lanman, but it works. On the old server, I can login, map the drives and run executables and use the dbf data files. It seems to me as if there is some configuration flag where the default has from 3.0 to 3.2 that I can't find. I did a detailed view of both config files from swat and ran a dif on them. I was unable to identify a place that could be changed that would allow the dos machines to utilize the samba file server. I am willing to use either different client software on the dos stations, or update the samba setup to a different version. I like ubuntu, but am not wedded to it. However, the dos stations must stay, even if I must maintain a server with 3.0 on it to keep them running. Any ideas? I am more that willing to RTFM, but have exausted my ideas of which FM and which part of it to read. Hints in this matter would be welcome. Hints on which config option in smb.conf would be even more welcome. Thanks in advance, Jim Hurlburt Atrium Windows and Doors Northwest. Yakima, WA USA -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
