On Mon, Jun 28, 2004 at 11:11:55AM -0500, Chris Garrigues wrote: > > From: Chris Garrigues <[EMAIL PROTECTED]> > > Date: Mon, 28 Jun 2004 10:01:55 -0500 > > > > I'm halfway there. It just failed with "defer sharing violations = Yes". > > I've changed the flag to "No". Since it doesn't always fail, I'll try all day > > to get it to fail. If it fails, I'll let you know. If it doesn't, I'll put > > it on my client's network this evening and let you know how well it works > > there. > > It just failed differently. Now after I tell it to go ahead and overwrite, it > hangs before trying to write the file and when it finally comes back it says: > > 'U:\bbu projection.xls' cannot be accessed. The > file may be read-only, or you may be trying to > access a read-only location. Or, the server the > file is stored on may not be responding. > > What a terribly written error message...not to mention that I can't believe > they can't tell the difference between a read-only file and the > server not responding. > > I had logging back down to 1 and this appeared in the log: > > [2004/06/28 11:02:37, 1] smbd/service.c:make_connection_snum(648) > callisto (10.1.1.186) connect to service groups initially as user cwg (uid=200 > , gid=100) (pid 731) > [2004/06/28 11:02:37, 1] smbd/service.c:make_connection_snum(648) > callisto (10.1.1.186) connect to service groups initially as user cwg (uid=200 > , gid=100) (pid 731) > [2004/06/28 11:02:37, 1] smbd/service.c:close_cnum(833) > callisto (10.1.1.186) closed connection to service groups > [2004/06/28 11:02:37, 1] smbd/service.c:close_cnum(833) > callisto (10.1.1.186) closed connection to service groups > [2004/06/28 11:04:38, 0] smbd/oplock.c:oplock_break(830) > oplock_break: end of file from client > oplock_break failed for file bbu projection.xls (dev = 809, inode = 1570136, > file_id = 23). > [2004/06/28 11:04:38, 0] smbd/oplock.c:oplock_break(923) > oplock_break: client failure in break - shutting down this smbd. > [2004/06/28 11:04:38, 1] smbd/service.c:close_cnum(833) > callisto (10.1.1.186) closed connection to service groups > [2004/06/28 11:04:38, 1] smbd/service.c:close_cnum(833) > callisto (10.1.1.186) closed connection to service cwg > > Chris > > P.S. I've turned oplocks off on the customer's server. Am I correct in > thinking that will mask the problem so they won't see it?
Yes, it will. Are you sure you're running the SVN code. I did fix a bug recently (friday I think) that would cause a client to get a double return from a rename which might have caused that. Unless it's that, it doesn't look like a deferred open problem. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba