On Wed, 9 Oct 2002, Kris Kelley wrote: > Two days ago I got a whole slew of smbfs errors in my system logs, all > stemming from an apparent inability to read two files. Here are some > samples: > > Oct 7 14:36:41 server kernel: smb_file_read: > cur/1033577524.16219.server.iatdev.com,S=230098@2,T > validation failed, error=4294967294
4294967294 is really -2, which is also -ENOENT. So the file is gone. (the printout is set to print as unsigned for some unknown reason) > Currently there are two servers that access the same SMB share (hosted > by a Windows 2000 Server machine), and it is entirely possible the other > server was accessing or even deleting these files while this server was > trying to read them. Could this have caused the error messages? It > seems strange that the server would try multiple thousands (!) of times > to access the files if this were the case. The -2 error code should make it back to the application. But if it doesn't check the returnvalue, or doesn't expect a ENOENT, it may continue trying. >From what I can tell, this isn't smbfs retrying it's the application. Any idea which application that may be? Normal unix behaviour is of course that you'd still be able to read the file after it was gone. /Urban -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
