Re: [Samba] samba + xp "Delayed Write Failed"
On Fri, Jul 08, 2005 at 03:21:57PM +0200, Kosa Attila wrote: > On Fri, Jul 08, 2005 at 03:11:45PM +0200, Kosa Attila wrote: > > > > I append the tcmpdump (egrep) issue and smb.conf-sambaversion. > > Sorry, stranded :) Sorry, I don't send :( http://members.chello.hu/kosa.attila/smb.conf-2.2.3a-15.gz http://members.chello.hu/kosa.attila/smb.conf-2.2.9-0.gz http://members.chello.hu/kosa.attila/tcpdump-2.2.3a-15.dmp.gz http://members.chello.hu/kosa.attila/tcpdump-2.2.9-0.dmp.gz -- Udvozlettel Zsiga Sorry, for my poor English! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + xp "Delayed Write Failed"
On Fri, Jul 08, 2005 at 03:11:45PM +0200, Kosa Attila wrote: > > Every test under running tcpdump: > tcpdump -ni eth1 -w tcpdump.dmp > tcpdump -ln -r tcpdump.dmp -s 0 -xX less 150 \ > | egrep "^SMB P" > tcpdump-sambaversion.dmp > > I append the tcmpdump (egrep) issue and smb.conf-sambaversion. Sorry, stranded :) -- Bye Zsiga Sorry, for my poor English! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + xp "Delayed Write Failed"
Hello! I testing samba and XP (file size ~14MB). Copy, 2.2.3a-15 samba->XP (Explorer) Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75:4723 751 to 825: 66 76 to 150: 490 826 to 900: 1 151 to 225: 201 901 to 975: 0 226 to 300: 4 976 to 1050: 7 301 to 375: 0 1051 to 1125: 1 376 to 450: 3 1126 to 1200: 0 451 to 525: 3 1201 to 1275: 0 526 to 600: 0 1276 to 1350: 194 601 to 675: 0 1351 to 1425: 2 676 to 750: 3 1426 to 1500+: 10300 Copy, 2.2.9-0 samba->XP (Explorer) Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75:4699 751 to 825: 103 76 to 150: 503 826 to 900: 1 151 to 225: 16 901 to 975: 0 226 to 300: 171 976 to 1050: 11 301 to 375: 0 1051 to 1125: 2 376 to 450: 4 1126 to 1200: 1 451 to 525: 3 1201 to 1275: 0 526 to 600: 0 1276 to 1350: 174 601 to 675: 0 1351 to 1425: 2 676 to 750: 4 1426 to 1500+: 10297 Copy, 3.0.14a samba->XP (Explorer) Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75:4718 751 to 825: 21 76 to 150: 481 826 to 900: 0 151 to 225: 11 901 to 975: 0 226 to 300: 222 976 to 1050: 0 301 to 375: 1 1051 to 1125: 2 376 to 450: 1 1126 to 1200: 0 451 to 525: 1 1201 to 1275: 0 526 to 600: 0 1276 to 1350: 217 601 to 675: 0 1351 to 1425: 2 676 to 750: 2 1426 to 1500+: 10305 Copy, 3.0.20pre1-1 samba->XP (Explorer) Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75:4683 751 to 825: 103 76 to 150: 494 826 to 900: 0 151 to 225: 12 901 to 975: 0 226 to 300: 178 976 to 1050: 7 301 to 375: 1 1051 to 1125: 1 376 to 450: 4 1126 to 1200: 1 451 to 525: 0 1201 to 1275: 0 526 to 600: 0 1276 to 1350: 179 601 to 675: 0 1351 to 1425: 1 676 to 750: 4 1426 to 1500+: 10298 I not see here significant difference. Program running, 2.2.3a-15 samba Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75: 12920 751 to 825: 469 76 to 150:1780 826 to 900: 2 151 to 225: 528 901 to 975: 0 226 to 300: 216 976 to 1050: 0 301 to 375: 1 1051 to 1125: 3 376 to 450: 6 1126 to 1200: 1 451 to 525: 1 1201 to 1275: 1 526 to 600: 1 1276 to 1350: 1 601 to 675: 1 1351 to 1425: 390 676 to 750: 3 1426 to 1500+: 28431 Program running, 2.2.9-0 samba Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75:8041 751 to 825: 470 76 to 150: 186872 826 to 900: 2 151 to 225: 132 901 to 975: 3 226 to 300: 218 976 to 1050: 4 301 to 375: 1 1051 to 1125: 1 376 to 450: 6 1126 to 1200: 1 451 to 525: 1 1201 to 1275: 0 526 to 600: 1 1276 to 1350: 1 601 to 675: 1 1351 to 1425: 346 676 to 750: 3 1426 to 1500+: 28430 Program running, 3.0.14a samba Packet Size (bytes) Count Packet Size (bytes) Count 1 to 75: 10179 751 to 825: 469 76 to 150: 225618 826 to 900: 2 151 to 225: 145 901 to 975: 0 226 to 300: 232 976 to 1050: 0 301 to 375: 12 1051 to 11
Re: [Samba] samba + xp "Delayed Write Failed"
On Thu, Jul 07, 2005 at 03:07:56AM -0700, Jeremy Allison wrote: > On Thu, Jul 07, 2005 at 11:53:39AM +0200, Kosa Attila wrote: > > >max xmit = 8192 > >block size = 4096 > > Why have you changed these ? What was the purpose of doing so ? > Just remove them from your smb.conf. My disks block size is 4096 byte. We tried all kinds of value to both options, in order to find the optimal values. man smb.conf (samba 3.0.14a version) /max xmit \(G\) The default is 65535, which is the maximum. In some cases you may find you get better performance with a smaller value. Therefore we tried to lower the default value. But we tried the default value, too. Unfortunately it hasn't changed for the better :( I make a little drawing to make the network topology clear (it may help). | WIN | | NT 4 | |1000 | |-firewall--Internet -- 100 1000 | --- | | samba |--|switch|| XP | |VNC | PDC| | VNC | | | LDAP || | | | | replica||1000 | | | --| --- | |1000MB| my | eth1 | cable| Linux| |samba |---| | box | |3.0.20| samba PDC eth0 192.168.3.35 (192.168.3.0/24) samba 3.0.20 eth0 192.168.3.190 (192.168.3.0/24) samba 3.0.20 eth1 192.168.20.1 (192.168.20.0/24) XP nic1 192.168.3.191 (192.168.3.0/24) XP nic2 192.168.20.2 (192.168.20.0/24) WIN NT 4192.168.3.21 (192.168.3.0/24) -- Bye Zsiga Sorry, for my poor English! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + xp "Delayed Write Failed"
On Thu, Jul 07, 2005 at 11:53:39AM +0200, Kosa Attila wrote: >max xmit = 8192 >block size = 4096 Why have you changed these ? What was the purpose of doing so ? Just remove them from your smb.conf. Jeremy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba + xp "Delayed Write Failed"
Hello! Hardver: Windows XP Compaq Proliant DL360, Linux Compaq Proliant DL380. 2 pieces of processors Intel Xeon 3,2GHz, 2GB RAM, 6 gigabit interface (2 tg3, 4 e1000), Debian Woody, 2.4.31 vanilla kernel. 6 U320 SCSI 15krpm HDD, 2 HDD RAID1 system, 4 HDD RAID1+0 data. Every network cards connect at speed of 1000MB full duplex, with XP crosscable (but we've tried with gigabit switch, too, we have tried both types of cards). In the XP's (there are more of them) there are 2 pieces of interface at gigabit speed, one of them is connected to the network of PDC, the other is connected to the cards of the above mentioned computer with crosscable. There is also a Windows NT 4.0 SP6 server with gigabit card, too. Surroundings: Windows domain, samba PDC (2.2.8a) that gets users from LDAP. The Linux computer belongs to the domain, the LDAP-server is set to it in libnss-ldap.conf file (the "getent passwd" sees the users and groups), and the samba is able to authentify the users with the help of the options "security = server, password server = IP.address", there's no problem with this. DL380 the samba's version is: 2.2.3a-15. Its speed is convencing, the program mentioned below communicates with the server at a speed of 140-15kbit/s (measuring with iptraf, Incoming ~9, Outgoing ~5), by the netwatch of Windows the utilization of the network sometimes reaches the 19%. When I make run the program below onto files on an XP, then by the network of Windows the utilization of the net is never higher than 15%. The utilization of the processor on the XP is above 50% while the program is running. There's a program that - when running on the XP - reads from mapped network drive and writes back there. It reads certain data and generates different files from the data. These files are relatively big size (both the read and written ones), now the biggest is the size of 400MB. However undefinable times we get the next error message in Windows: "Delayed Write Failed". This time a note gets also into the diary of the events, its the status code is: c20c (see later why it's important). Searching in the Microsoft's Knowledge Base we've found these messages that are like the error message above: http://support.microsoft.com/default.aspx?scid=kb;en;321733 - here the error message is the same but the status code is not. It seems that the SP2 solves this problem on XP, we've looked through the mentioned things and everything is OK, they are set up so that they should work. http://support.microsoft.com/default.aspx?scid=kb;en-us;Q293842 - the error message is similar, the status code is the same, too but by Microsoft this error doesn't happen on XP. http://www.tangent-systems.com/support/delayedwrite.html - this is a good summary of the problem above. It analyses what kind of settings are needed for servers and clients in order to avoid this error (that is depending on the combination of the server and the client to switch on or to switch off the SMB signing). On the basis of the last link we have checked the settings of the Windows NT server (on that making the program run the error message doesn't happen) and they suit the requirements written in the article. The 2.2.3a-15 samba Windows NT behaves as a server on the network, that is SMB signing should be switched off in it, too... however this version doesn't know such an option! (I can't understand, if it doesn't know the option of SMB signing how it can use? Otherwise, if this samba can't use it, it can't be switched off because it is not switched on...) Anyway, we've also tried 2.2.8, 2.2.9 versions, but there was no result beside the drastic slowing down, the error message arises again on XP. (Drastic slowing down means: the speed doesn't exceed 2kbit/s in contradiction to the previous 15kbit/s, Incoming ~10700, Outgoing ~8500). We have ported 3.0.14a and 3.0.20pre1-1 versions aswell, they have SMB signing option (client signing = diabled, server signing = disabled), and it solves the question of error. Using these versions the error message doesn't arise on XP. But the speed is awful! We aren't able to reach 3kbit/s :( If debug level = 3, even 2kbit/scan't be exceeded! On XP the utilization of the processor doesn't go over 27%! By the Windows netwatch the utilization of the network never exceeds 2%! The utmost packet size (with iptraf) 76-150 byte. It's interesting that in case of simple copy (that is I copy from samba to XP starting copy from XP with Explorer) by the Windows netwatch speed is fixed 11%, by iptraf it is roughly fixed 117000kbit/s (with version 2.2.3a-15). And neither copies always run without errors! Sometimes an error message arrives: "Network name can't be reached" (or something like that - it can't be totally reproducted the copy is sometimes successful, sometimes not). Here is the 2.2.3a-15 samba version's smb.conf file (as it can be seen, we haven't tuned too much on it, it's almost the default config)
