I think that the original poster knew that this patch hadn't been applied and was suggesting that it should be. I've just been chasing down a problem with a user logging out from a samba controlled domain and receiving error messages about some files. On logging back in the user would receive errors about the same files and they would be shunted to a temporary profile. What was/is happening is that the locks aren't getting released on some of the file. Sometimes you actually end up with a stuck smbd process as well, which only kill -9 will terminate. In this case the use has a lot of temporary files, 7-50Mb in size, that a piece of commercial software seems to enjoy creating in the profile. Logging in/out, particularly over a wireless network seem to cause these files to end up as stuck locks. With the patch listed you get a more controllable result -- you may still get a stuck process at times with some of the locks in but the user can continue to log in and out. It's obviously not an ideal solution because the system is still generating the lock issues in the first place and you can end up with the stuck smbd process, but at least you don't have to stop samba, kill -9 any remaining smbd process and then start samba every time the user logs out! (It also significantly speeds up the log in/out process in these cases)
-- "Trying to delay for oplocks twice" bug https://bugs.launchpad.net/bugs/84923 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
