I've compiled Samba (2.2.5) on Linux with quotas and they work. But Windows users don't receive warning messages when they over quota. I've tested Samba with Windows Explorer and FAR (file manager written by Eugene Roshal). When user have 100 MB free on his homedir and try to copy file 200 MB with Explorer, Samba "allow" it him! Actually this file (200 MB) is damaged. When user create file by any application (for example MS Word) and then try to save it, he receive warning message (Insufficient disk space). When user use FAR and try to copy file, he receive warning message (Insufficient disk space). I've found option "strict allocate" in smb.conf. It's "NO" by default. When I've changed it to "YES" Samba's behaviour has been changed. When user try to copy file 200 MB with Explorer, he receive warning message (Insufficient disk space). When user use FAR and try to copy file, Samba "allow" it him! Actually this file (200 MB) is damaged. When user create file and then try to save it, he don't receive warning message and this file (200 MB) is damaged. I think this behaviour of Samba is incorrect. What's wrong and how to fix this problem?