[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
Re: [Samba] Re: Delayed Write Failed and other similar errors on Windows machines
On Sat, Feb 05, 2005 at 01:07:38AM -0800, Michael J. Welch, Ph.D. wrote: I installed Samba 3.0.11, and the same problems are there. Looks like it might be a hardware problem on your network then. 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? Probably, but it might just confirm you have a network problem. Jeremy. -- 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
