[Samba] File validation errors?

[Kris Kelley]

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 at 2,T
      validation failed, error=4294967294
   Oct  7 14:36:47 server last message repeated 5984 times
   Oct  7 14:36:47 server kernel: smb_file_read:
      cur/1033577524.16219.server.iatdev.com,S=230098 at 2,T
      validation failed, error=4294967294
   Oct  7 14:36:47 server last message repeated 36 times
   Oct  7 14:36:47 server kernel: smb_file_read:
      cur/1033577524.16219.server.iatdev.com,S=230098 at 2,T
      validation failed, error=4294967294
   Oct  7 14:36:47 server last message repeated 36 times

   Oct  7 14:41:53 server kernel: smb_file_read:
      cur/1034013088.13474.server.iatdev.com,S=263201 at 2,T
      validation failed, error=4294967294
   Oct  7 14:42:25 server last message repeated 43245 times
   Oct  7 14:42:35 server last message repeated 19848 times

   Oct  7 14:43:36 server kernel: smb_file_read:
      cur/1034013088.13474.server.iatdev.com,S=263201 at 2,T
      validation failed, error=4294967294
   Oct  7 14:43:37 server last message repeated 598 times

This happened over the course of about 7 minutes (the first and last
relevant log entries are shown above), and affected only the two files
listed.  Does anybody know what may have caused this?  If it's something
to worry about, what can I do to prevent it from happening again?

I found in the list archives where a person got a batch of similar log
entries, and it was suggested this was due to the SMB connection being
dropped.  I do not believe that is the case here, because there were no
SMB connection errors logged during this time frame.

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.

I'm running Red Hat's release of kernel 2.4.9-34 for Red Hat 7.1.  Any
insight will be appreciated.  If more info is needed, just let me know.
Thanks!

---Kris Kelley