X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=UJO+1vtnRa1Ja/Tmd5zTw/vi1yZSPlWybCvE7SUnfzoTc/YvPJ0H6
	VacNYUw0Z8pi1AaJUa9gLi2M29uwgDhkZI2/LRGVTLK7QGc4TKQO5/kpRawDxbgb
	EWDszX/l7CvxELQnJFrLBM+BDDhNM+u+c2AUfbrSY9jKcSAdealB2g=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	 bh=gH87MryMVyI6tlGZ4Zu/8I4BIfs=; b=spnJPpsNZHukNdGLqHNl1UfUeuFY
	MTHHUUnockatyQTykzs2yYgP0JcfT63tyjbkSJaL2OFj+r1d8Q23Fh3wMZu17u1p
	GJWWK6vNS8yzf923q45M4FlWiUfWfjCVIPTtaCRiPYAqY964rmgY5FQvnls6GcFy
	6w2eLHT+3OEiL5U=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-4.7 required=5.0 tests=AWL,BAYES_00,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2
X-HELO: plane.gmane.org
To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@NexGo.DE>
Subject: Re: Why does df fail to stat CIFS shares?
Date: Wed, 27 Aug 2014 16:28:05 +0000 (UTC)
Lines: 47
Message-ID: <loom.20140827T181656-215@post.gmane.org>
References: <20140627143626.GA9220@F1S712WWS> <20140703094152.GB1803@calimero.vinschen.de> <loom.20140826T110928-929@post.gmane.org> <20140826124557.GB5740@calimero.vinschen.de> <loom.20140827T165747-369@post.gmane.org> <20140827151536.GK20700@calimero.vinschen.de> <20140827153700.GL20700@calimero.vinschen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> > -v, please.  What means "obviously" here?  Did you ask Netapp?

No, I've tried all combinations of parameters to the open calls to
absolutely no avail.  I then started to look at what the VolumeInformation
call is supposed to be doing and decided that this might have a better
chance of producing a workaround.

> > The FileFsFullSizeInformation class is *old*, it has been introduced
> > with Windows 2000.  Did you test all combinations I asked you for?  Can
> > you provide detailed results?  It might help to find a working combination.

All combinations you listed produced absolutely the same behaviour than
before: the open suceeds and the VolumeInfo call fails.  I've tried a few
other combinations that are forbidden according to MSDN and promptly had the
open call fail, so I think I did this correctly...

While searching the net I've found some notes saying that the only classes
confirmed working everywhere didn't include FileFsFullSizeInformation.  True
or not, that's what pushed me to rip it out.

http://sourceforge.net/p/openxdk/patches/_discuss/thread/4b412944/4ba5/attachment/undocumented.txt

> Btw., one other hare-brained idea would be if the Netapp FS has a
> somewhat different idea of the size of FILE_FS_FULL_SIZE_INFORMATION,
> maybe due to a misunderstanding in alignment.  What you could try is
> to make full_fsi a pointer:
> 
>   PFILE_FS_FULL_SIZE_INFORMATION full_fsi =
>   	(PFILE_FS_FULL_SIZE_INFORMATION)
> 	alloca (2 * sizeof (FILE_FS_FULL_SIZE_INFORMATION));
> 
> and then change all "full_fsi." to "full_fsi->"

Tomorrow...

> If nothing else works, try this workaround for size:

That's essentially what I've done to get it working.  Not that exact patch,
so I'll try that out tomorrow as well, but that code path should produce
correct output from df no matter of what FS it finds behind the mount.


Regards,
Achim.




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple