From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Why does df fail to stat CIFS shares?
Date: Thu, 28 Aug 2014 15:12:00 -0000 [thread overview]
Message-ID: <20140828151207.GY20700@calimero.vinschen.de> (raw)
In-Reply-To: <loom.20140828T165427-636@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
On Aug 28 14:58, Achim Gratz wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> > >
> [...]
>
> The patch with the fallback to FileFsSizeInformation works as expected.
>
> > > > 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:
>
> The FileFsFullSizeInformation path still fails with the same error code even
> with these changes (I've added a few debug_printf to show the results even
> in the case of success):
>
> 31 3473313 [main] df 28752 statvfs: (/home/gratz, 0x28A864),
> file_attributes 48
> 1186 3474499 [main] df 28752 fhandler_disk_file::fstatvfs: 0xC000000D =
> NtQueryVolumeInformationFile(\??\H:\GNU, FileFsFullSizeInformation)
> 479 3474978 [main] df 28752 fhandler_disk_file::fstatvfs: 0x0 =
> NtQueryVolumeInformationFile(\??\H:\GNU, FileFsSizeInformation)
> 1709 3476687 [main] df 28752 fhandler_disk_file::fstatvfs: 0 =
> fstatvfs(/home/gratz, 0x28A864)
> 34 3476721 [main] df 28752 statvfs: 0 = statvfs(/home/gratz,0x28A864)
#$%@ netapp #@$%
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 --]
next prev parent reply other threads:[~2014-08-28 15:12 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
2014-08-28 14:58 ` Achim Gratz
2014-08-28 15:12 ` Corinna Vinschen [this message]
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=20140828151207.GY20700@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).