From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Link count wierdness
Date: Thu, 17 Jul 2014 19:43:00 -0000 [thread overview]
Message-ID: <87k37bvkib.fsf@Rainer.invalid> (raw)
In-Reply-To: <20140717183915.GT15332@calimero.vinschen.de> (Corinna Vinschen's message of "Thu, 17 Jul 2014 20:39:15 +0200")
Corinna Vinschen writes:
> Netapp inode numbers are not reliable and thus the number of links isn't
> either. There's a check in Cygwin which is the result of the early
> Cygwin 1.7 development. It does not report the number of hardlinks
> and it fakes the inode numbers on netapp filesystems.
Ah OK, that explains the wierd output from fstat. Is there a windows
program to query that information, perhaps?
> The file system returns STATUS_INVALID_PARAMETER when calling
> NtQueryVolumeInformationFile(FileFsFullSizeInformation) for some
> reason. If you're set up to build your own Cygwin DLL, we could
> perform two or three really quick tests to find out if there's a way
> to workaround this issue in Cygwin.
I am not yet but might be interested, is there a description somewhere
of what that takes? I would need to use Git (is it ready yet?) since
CVS gets blocked by the firewall and the various scrapers using CVSweb
don't really work that well.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
--
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
next prev parent reply other threads:[~2014-07-17 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 18:09 Achim Gratz
2014-07-17 18:39 ` Corinna Vinschen
2014-07-17 19:43 ` Achim Gratz [this message]
2014-07-17 20:07 ` Christopher Faylor
2014-07-18 4:30 ` Achim Gratz
2014-07-18 6:05 ` Andrey Repin
2014-07-18 18:59 ` Christopher Faylor
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=87k37bvkib.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).