A bit of google revealed that setting "strict allocate = on" may fix
this.
I don't understand this completely, but it may be worth a try:
from man smb.conf again:
strict allocate (S)
This is a boolean that controls the handling of disk space allocation in
the server. When this is set to yes the server will change from UNIX behaviour
of not committing real disk storage blocks when a file is extended to the
Windows behaviour of actually forcing the disk system to allocate real storage
blocks when a file is created or extended to be a given size. In UNIX
terminology this means that Samba will stop creating sparse files. This can be
slow on some systems.
When strict allocate is no the server does sparse disk block allocation
when a file is extended.
Setting this to yes can help Samba return out of quota messages on systems
that are restricting the disk quota of users.
Default: strict allocate = no "
On Fri, 09 Sep 2005 13:04:47 +1200
Roger Searle wrote:
--
Nick Rout <[EMAIL PROTECTED]>
