[Samba] "Delayed Write Failed" and other similar errors on Windows machines
On Saturday 05 February 2005 13:25, Jeremy Allison wrote: > Looks like it might be a hardware problem on your network then. Friday May 24, my windows machine corrupted itself to the point of failure (as it does about twice a year), and I was forced to reload from scratch (a two day job). After the reload, I tested the "'Delayed Write Failed' and other similar errors on Windows machines" problem I had reported a few months ago, and (surprise) the problem magically went away. I have not made any changes to Samba in the interval. It is a known fact that Windows corrupts itself over time, and based on this experience, it would seem reasonable to consider testing suspected Samba bugs on a test machine with a clean install of Windows before accusing Samba. Case closed. Thanks to all. -- Mike Michael J. Welch, Ph.D. [EMAIL PROTECTED] or [EMAIL PROTECTED] Always remember that a parrot is not merely a pet: it is a child from another world. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: nazi spam in German over list address
On Monday 16 May 2005 19:29, Eric Hines wrote: > Locking out the Windows folks is counterproductive--those are exactly the > ones we're trying to attract away from MS, for that's the only way we'll > beat MS--by converting its customers. > Everybody who receives this samba email signed up for it. Why not only propagate messages from people on that list? After all, as it is now, if you want to get help from other people on the list, you'll probably sign up. I understand that someone could publicly post, then read the list from some other source than the emails, but that seems like the hard way. It's just not that hard to sign up, and it's just as easy to drop off the list later. -- Mike Michael J. Welch, Ph.D. [EMAIL PROTECTED] or [EMAIL PROTECTED] La perfection est atteinte non quand il ne reste rien à ajouter, mais quand il ne reste rien à enlever. --Antoine de Saint Exupery (Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away.) Svp, rappelez-vous toujours, un perroquet n'est pas simplement un animal de compagnie. C'est un enfant d'un autre monde. -- Bill Kiesselbach. (Please, always remember, a parrot is not merely a pet. It is a child from another world.) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Horrendously slow transfer speeds in FC3 is driving me crazy!!! Please help...
For what it is worth, I have a Windows XP Athlon 2600 machine with 1GB RAM and a 100MBit LAN over CAT5, and a SuSE Linux dual Pentium III 1GHz machine with 1GB RAM running Samba 3.0.10. Actually, a very simple configuration. I measured my transfer rate from the Linux box to the Windows box by copying a 1.8GB file. The transfer speed was 8.85MB/Sec, or 80% of the 100MBit rating of the network. A SCSI to EIDE ATA disk-to-disk transfer on the Linux box of the same file was 16.7MB/Sec. -- Mike Michael J. Welch, Ph.D. [EMAIL PROTECTED] or [EMAIL PROTECTED] La perfection est atteinte non quand il ne reste rien à ajouter, mais quand il ne reste rien à enlever. --Antoine de Saint Exupery (Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away.) Svp, rappelez-vous toujours, un perroquet n'est pas simplement un animal de compagnie. C'est un enfant d'un autre monde. -- Bill Kiesselbach. (Please, always remember, a parrot is not merely a pet. It is a child from another world.) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: simple samba example problem
On Saturday 26 February 2005 15:16, tasos wrote: > Hello people. > I have used all the simple smb.conf that i found at > samba.org. Restart nmb when you restart Samba: cd /etc/init.d ./smb stop ./nmb restart ./smb start If you are trying to login from Windows, you have to reboot your Windows machine. Windows will still be holding the old values in cache otherwise. -- Mike -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: "Delayed Write Failed" and other similar errors on Windows machines
Günter, I got the ethereal capture files under Samba, one without the "Delayed Write Error," one with, and one using Windows File server for reference. You can get them at ftp://chata.dyndns.org/DelayedWrite.zip Please see the readme.txt file. I got a big surprise when I examined the capture files. I imagine you speak German. I speak English, French, and Spanish. As far as my German goes, "Ich habt Deutsch ein der hochschule gelernt, aber ich habt alles vergessen." Désolée monsieur. I hope this is useful--I spent some long hours preparing it. -- Mike On Sunday 06 February 2005 17:27, you wrote: > Hello Michael, > > > On Saturday 05 February 2005 13:25, Jeremy Allison wrote: > > > Looks like it might be a hardware problem on your network then. > > > > I noticed that moving the offending folder and files on the Windoze end > > to another folder on the Samba share, the problem seemed to go away. I > > haven't had time to run any other tests, but if the the problem shows > > back up, I'll do an etherreal capture to see what can be learned. > > > > For now, case closed. Thanks. > > > > -- Mike > > -- > > sorry Mike, if you dislike getting private email resulting from public > news-groups posts. :-) > > I'm somewhat supporting the samba 4.0 team - but also watch 3.0.x. > > If your discussed problem is showing up again, feel free to contact me > directly. > > To get a chance for analysing it, you should try to catch > - a samba debug log level 10 > - an ethereal trace > > Both should be "as close to the problem as possible" - hopefully not > megabytes. You can switch the samba debuglevel (on your linux machine) with >smbcontrol smbd debug 10 > (by default this logfile is written to /var/log/samba/log.smbd) > btw - don't forget to reset that debug stuff (after sniffing the bug)! > smbcontrol smbd debug 0 > > And please, also include your used samba version. > > Maybe i can help > > Cheers, Guenter > > btw - you really get that error, if your "hardware link" - network cards, > cables and so on are not working properly or are out of specs. > So, also your link-speed (10 / 100 / 1000 Mbit) (full / half duplex) and > the involved switches or hubs could add some problems, too. -- Mike Michael J. Welch, Ph.D. [EMAIL PROTECTED] or [EMAIL PROTECTED] La perfection est atteinte non quand il ne reste rien à ajouter, mais quand il ne reste rien à enlever. --Antoine de Saint Exupery (Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away.) Please, always remember, a parrot is not merely a pet. It is a child from another world. -- Bill Kiesselbach. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: "Delayed Write Failed" and other similar errors on Windows machines
Bob, I tried copying the failing directory on my Windows machine to make a "backup" copy of the failing directory. When I tested it as I had before, it ceased to fail. I copied the original to see what would happen, and the "Delayed Write Failed" disappeared there as well. Now I haven't had the problem repeat for a while, nor do I expect it to return. Also, the problem appeared before in any similar directory (Windows C++ projects), but now none are failing. I have no idea what made the problem go away, whether it was bad blocks on the Samba hard disk, or some setting in the smb.conf file. I think it is unlikely the hard disk has a problem because it was recently reinitialized and it is a Raid-0 mirrored drive. I know it was not corrected on the Windows side. It was corrected as a result of some change I made on the Samba side. I did notice that nmb must be restarted with samba after the smb.conf is changed. cd /etc/init.d ./smb stop ./nmb restart ./smb start I also noticed that Windows must be restarted at the same time, or Windows will not see the smb.conf change. (What a pain in the ash! It takes my Windows machine 5 minutes to restart.) You can see my smb.conf at ftp://chata.dyndns.org/smb.conf I know this conf file is working, so these settings are OK. You might want to test these global settings on your machine to see if it gets rid of the problem. Hope this is of use to you. -- Mike On Friday 11 February 2005 05:48, Robert M. Martel wrote: > ... > Anyhow, for the users that were changed I have see many "Windows Delayed > Write Failed" error messages. > ... > -Bob Martel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: "Delayed Write Failed" and other similar errors on Windows machines
On Saturday 05 February 2005 13:25, Jeremy Allison wrote: > Looks like it might be a hardware problem on your network then. I noticed that moving the offending folder and files on the Windoze end to another folder on the Samba share, the problem seemed to go away. I haven't had time to run any other tests, but if the the problem shows back up, I'll do an etherreal capture to see what can be learned. For now, case closed. Thanks. -- Mike -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: "Delayed Write Failed" and other similar errors on Windows machines
On Friday 04 February 2005 16:10, Jeremy Allison wrote: > What messages are you getting in the Samba logs ? This looks like an > oplock break failure or in the extreme case smbd crash. > > Jeremy. I installed Samba 3.0.11, and the same problems are there. I'm wondering if this could be what's going on: I try to delete a file and Samba deletes it, but returns a code Windoze doesn't understand; then Windoze tries to repeat the attempt to delete the file, but the second time it finds no file (because it actually was deleted on the first attempt), then Windoze reports that the file cannot be deleted because there is no file. Would an etherreal capture log be of any help? -- Mike Michael J. Welch, Ph.D. [EMAIL PROTECTED] or [EMAIL PROTECTED] La perfection est atteinte non quand il ne reste rien à ajouter, mais quand il ne reste rien à enlever. --Antoine de Saint Exupery (Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away.) Please, always remember, a parrot is not merely a pet. It is a child from another world. -- Bill Kiesselbach. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: "Delayed Write Failed" and other similar errors on Windows machines
On Friday 04 February 2005 16:10, Jeremy Allison wrote: > > What messages are you getting in the Samba logs ? This looks like an > oplock break failure or in the extreme case smbd crash. > > Jeremy. On Windoze: It doesn't seem like smbd is crashing because it continues to work after the errors. For example, I go to a folder and try to delete--I get an error, but the file deletes. I try to delete another and it deletes with no error. I go up to the folder's parent, then back into the folder, and try to delete again, and the error repeats. In all this, certain operations always work, such as reading a file. I did notice that in the log.linux there is a message "Mapping user [TUX-NET]\[linux] from workstation [LINUX]"--this may refer to the SuSE Live DVD connect, but I logged on with a proper username and password. BTW, the delayed write failed error does not occur if I use a share on a windows machine, only on the SuSE machine. I used the same 3.0.7 under Mandrake without this problem, so perhaps it has something to do with the SuSE configuration. The logs and smb.conf can be found at ftp://dev.horchatafactory.com/ I was out of the office today, and I just turned on my Windoze machine to repeat the error, and it isn't showing up at this moment. Usually a Windows reboot has no effect on the problem. This is the first time I've seen the problem go away without a SuSE reboot, and SuSE was last rebooted 2 days 9 hours ago. -- Thanks, Mike -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] "Delayed Write Failed" and other similar errors on Windows machines
I am experiencing an error which has been reported on the internet
since Samba 2.2.7 and Windows 2000. There are many suggestions as
to the cause of this problem, but no working solutions that I've been
able to find. I've already invested two weeks on this problem.
I was running Samba 3.0.7 under Mandrake for the last year, and
this problem was not present. Because Mandrake had other bugs,
and got worse upgrading from 10.0 to 10.1, I switched to SuSE 9.2
professional (boxed set). The problem does not manifest itself for
the first few hours after booting, then it shows up. The only way
I have found to get rid of the problem (for a short while) is to
reboot Suse, an obviously unworkable workaround. I am currently
running Samba 3.0.7 under SuSE, but I tried Samba 3.0.10 with no
difference.
My server is a Dual SMP Pentium III with 1GB RAM, a 60GB
Maxtor for the system drive, and a 3Ware raid and two 80GB Maxtor
drives in a RAID 1 configuration for the data drive. This is the
same machine the Mandrake was running on.
Here I have listed typical errors I get under the SuSE/Samba 3.0.7:
[An attempt to copy a file.]
The specified network name is no longer available.
[The file is not copied, but the name is placed into the directory.
A second attempt works normally, unless one backs out of the folder,
then comes back in again, in which case the failure is repeated.]
[An attempt to open a VS C++ project with no .NCB file. VS tries to
build another file, but fails during the write.]
Windows - Delayed Write Failed
Windows was unable to save all the data for the file
\\Server\icr\active\Copy of Ctrl 4-3-1-33\SKAN_Talk.ncb. The data has
been lost. This error may be caused by a failure of your
computer hardware or network connection. Please try to save
the file elsewhere.
[The file is partially created.]
[An attempt to delete a file after entering the folder.]
Cannot delete ~VC72: Cannot find the specified file.
Make sure you specify the correct path and file name.
[The file is deleted. An attempt to delete another file
without first exiting and reentering the folder succeeds
without any error.]
I also tried booting SuSE 9.2 DVD LIVE, and I opened /tmp,
then copied a file (vmlinuz) to it a half dozen times or more.
After the first time, I selected OVERWRITE each time.
Then I tried to delete the file, and got a message stating
that the file was in use and could not be deleted. After
restarting nmb/smb at the Samba server, the file could be deleted.
Note that copying and overwriting the file 2 or 3 times was not
enough. The file had to be overwritten at least half a dozen times
or so. Since this is a SuSE to SuSE test, it eliminates Windows as
the problem, and remember, the problem did not present itself
under Mandrake with the same Windows client machine.
Here I have listed some of the main things I have tried to fix it:
In Windows XP Pro SP1, I have tried setting the registry entries for:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\...
Memory Management\SystemPages
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanserver\...
Parameters\{EnableOplocks|EnableSecuritySignature)
but with no effect. I also made sure that there were adequate
permissions, as evidenced by the fact that the second attempts
would succeed.
In Samba, I changed/added the following and many other variations
with no effect:
[global]
use sendfile = yes/no
large readwrite = yes/no
admin users = mike
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_KEEPALIVE \
SO_RCVBUF=65536 SO_SNDBUF=65536
server signing = disabled
client signing = disabled
level2 oplocks = yes/no
locking = yes/no
[each share]
create mask = 0660
directory mask = 0774
oplocks = no
I find it difficult to understand how this has been able to be a known
(and very serious) problem for many years without being addressed
and fixed. Surely someone must know the solution to this problem.
Is it Samba or is it SuSE? What do I have to do to fix it?
Any help will be greatly appreciated.
-- Mike
[EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
