Re: [Samba] Samba <-> Vista RTM interoperability issue

Alexander forsmb at
Tue Dec 19 12:55:45 GMT 2006

Hm, after further investigation it turned out that the reason for such behaviour was autofs' --ghost directories and Vista's default approach: before writing Vista does QUERY_FS_INFO request regarding FS free space and for --ghost'ed dirs Samba returns 0... Older versions such as Win2003 and XP do not do such requests before writing.

Could someone tell me how Samba defines free space on the share as a response for such request (not sure, maybe such question is more relevant for samba-technical)? I've tried using usual Linux tools - df and du and it turned out that df returns 0 while du seems to return the correct value.


-----Original Message-----
From: Mav T <forsmb at>
To: samba at
Date: Mon, 18 Dec 2006 17:09:46 +0300
Subject: [Samba] Samba <-> Vista RTM interoperability issue

> Hi List!
> We've run into interesting problem with Samba and Vista.
> In short - there's a Samba server sharing NFS connection. What is shared is the NFS link mounted somewhere in root (say /nfspath) and [homes] which is in fact /nfspath/some/dir. And the problem is that Vista client can write a file onto the share using \\sambaserver\homes\dir notation, but cannot do it using \\sambaserver\nfspath\some\dir notation (which is in fact the same). The reason noted by Vista - no free space, <size of saved file> more  needed on the device.
> I've tried that on 3.0.22 and 3.0.23d versions - with the same result. Have someone met that and what could be the reason?
> Regards,
> Alexander
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:

More information about the samba mailing list