public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Why does df fail to stat CIFS shares?
Date: Wed, 27 Aug 2014 17:07:00 -0000	[thread overview]
Message-ID: <20140827170707.GN20700@calimero.vinschen.de> (raw)
In-Reply-To: <20140827170421.GM20700@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]

On Aug 27 19:04, Corinna Vinschen wrote:
> On Aug 27 16:28, Achim Gratz wrote:
> > 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., the document is from 2003.  11 years is a long time.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-08-27 17:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 14:36 Alexander Schwab
2014-07-03  9:41 ` Corinna Vinschen
2014-07-03 10:11   ` Alexander Schwab
2014-07-03 10:25     ` Corinna Vinschen
2014-07-03 11:14       ` Alexander Schwab
2014-07-03 11:33       ` Alexander Schwab
2014-08-26  9:15   ` Achim Gratz
2014-08-26 12:46     ` Corinna Vinschen
2014-08-26 15:01       ` Achim Gratz
2014-08-26 15:07         ` Corinna Vinschen
2014-08-26 17:01           ` Achim Gratz
2014-08-27  9:24           ` Achim Gratz
2014-08-27  9:57             ` Corinna Vinschen
2014-08-27 10:10               ` Achim Gratz
2014-08-27 15:06       ` Achim Gratz
2014-08-27 15:15         ` Corinna Vinschen
2014-08-27 15:37           ` Corinna Vinschen
2014-08-27 16:28             ` Achim Gratz
2014-08-27 17:04               ` Corinna Vinschen
2014-08-27 17:07                 ` Corinna Vinschen [this message]
2014-08-28 14:58                 ` Achim Gratz
2014-08-28 15:12                   ` Corinna Vinschen
2014-08-28 12:31               ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140827170707.GN20700@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).