samba - Oct 2008 - dfree causing write access problems

Hi I'm having problems with the dfree option on a Solaris 10  
fileserver. Specifically: I had 3.0.X on the fileserver and the dfree  
option worked fine. I upgraded to 3.2.2 and now if dfree is enabled  
the clients get 1MB reported as the size of the share and when a  
client tries to right to the system they get told that the filesystem  
is full. The script output has been tested throughly and reports:
<quoted size><space><free>

system: Solaris 10
base filesystem: SAM QFS 4.5 with quotas enabled

clients: variety, mostly Macs (Tiger and Leopard), some Windows and  
Linux

The idea is to use dfree to fake disk sizes so that it reports the  
quota size for a project and the amount that is still free rather than  
the base system size. This is very important to us as we have users  
with 50GB shares that are reporting 4TB or something whatever happens  
to be the free space on the array at the time. Using samba quotas  
isn't an option because we don't want two quotas to update and some  
project shares get NFS mounted as well, so we need the quotas down to  
the host filesystem level.

On Thu, Oct 09, 2008 at 11:30:21AM +0200, Mike Gallamore
wrote:
> Hi I'm having problems with the dfree option on a Solaris 10
fileserver.
> Specifically: I had 3.0.X on the fileserver and the dfree option worked 
> fine. I upgraded to 3.2.2 and now if dfree is enabled the clients get 1MB 
> reported as the size of the share and when a client tries to right to the 
> system they get told that the filesystem is full. The script output has 
> been tested throughly and reports:
> <quoted size><space><free>
>
> system: Solaris 10
> base filesystem: SAM QFS 4.5 with quotas enabled
>
> clients: variety, mostly Macs (Tiger and Leopard), some Windows and  
> Linux
>
> The idea is to use dfree to fake disk sizes so that it reports the quota 
> size for a project and the amount that is still free rather than the base 
> system size. This is very important to us as we have users with 50GB 
> shares that are reporting 4TB or something whatever happens to be the 
> free space on the array at the time. Using samba quotas isn't an option
> because we don't want two quotas to update and some project shares get 
> NFS mounted as well, so we need the quotas down to the host filesystem 
> level.
You may need to add some debug statements to smbd/quotas.c
to see where the size calculations are going wrong in the
Solaris codepaths. Unfortunately this is one of the most
system specific parts of Samba, so it'll be hard for others
to reproduce.

Jeremy.