On 04/24/09 00:45, Tal Tamir wrote:
Does this resolve the regression with oplocks?
The only CIFS service difference between 111 and 111a is that
oplocks are enabled in 111 and disabled in 111a.
108-110 have broken CIFS (just doesn't work), but I was warned against
using 111 until oplock regression (introduced in 110) is resolved, I was
told it would be in 112, but seeing as this IS a newer version than 111
(non a) I figured I'd ask
We've been recommending 112, which seems to have resolved problems
for many people but there have been a couple of problem reports with
112.
If you encounter a problem with Excel 2003 complaining that the file
may have been changed by another user, it is probably 6830187: False
message when saving a Excel 2003 file. This is due to a difference
between the way that UNIX file systems and NTFS handle the modified
time on files, and Excel 2003 expects NTFS behavior.
Workaround: disable oplocks.
There is one report of an idmap problem, which results in shares
becoming inaccessible. This is currently under investigation and
we're still looking for the root cause.
Updates in 113:
6817902 Join domain fails intermittently while running regression test
6818984 avscan + cifs is broken : cifs IO fails and vscan temp hangs
when accessing files to be scanned
6761634 When NT4 client copies a file with NTFS named streams,
NTFS named streams not copied
6642756 Cannot create the file with NTFS-stream at the same time
6827463 odir operations don't use the right cred when user has
privilege
6827904 Can't map a share from windows 98 client
6828595 Cannot rename a file from Windows 98 clients
Updates in 114:
6802098 Need to support name-based rules for builtin and local well
known accounts
6831172 smb_server.c is missing a few smb_server_release() calls
6831734 smbd exit on session reconnect with vc=0
6832258 System panics at smb_node_lookup+0x3c1
Notes:
The updates for 6831172 and 6831734 are highly recommended when 114
becomes available because, if they happen, you'll need to reboot
your system.
6832258 happens on tmpfs but is really unlikely on ZFS or any disk
based file systems. This should only affect people sharing, say,
/tmp, which I think is rare outside of our test groups.
Alan
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
