Hello! A good day to you all. we've recently had some problems with samba (2.2.0) and sourcesafe. We had one particular project with over 700 files on it, and we've just recently encountered some problems with it, i.e. "corrupted" files from sourcesafe. i've read the archives, and someone mentioned that the number is actually unlimited(or 6.4million at the very least)...so my theory of having too many files in a share just got shot down. Any ideas as to what's causing it? Is there something in the way sourcesafe handles files that samba doesnt like? Any comments are most welcome. __________________________________________________ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1
You did say any comments welcome: I'll put in my 2 cents. File corruption comes up on the list and I haven't seen a good explanation for it. If you use oplocks, on by default, windows caches the files. A nonwindows program on the samba server can access that file, without going through samba, and windows will never know it. That may cause file corruption. I don't know if NFS and samba play well together, either. Also, some programs may not lock files. Paint doesn't in windows, so more than one person can edit an image file simultaneously from different clients. So, the application may allow for file corruption.