From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Link count wierdness
Date: Thu, 17 Jul 2014 18:39:00 -0000 [thread overview]
Message-ID: <20140717183915.GT15332@calimero.vinschen.de> (raw)
In-Reply-To: <87oawnvovw.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
On Jul 17 20:09, Achim Gratz wrote:
>
> I have come across an interesting problem with the link count on a
> NetApp volume(*). While hardlinks can be created just fine and work as
> you'd expect (changing one file changes all the linked files), the link
> count that gets reported for each of the linked files is always 1. ONe
> of those NetApp volumes is my home directory and it breaks GNU parallel,
> which uses the link count as a semaphore. Is this a bug in how Cygwin
> handles these volumes or a problem in how they are set up or something
> entirely else?
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.
> (*) df also doesn't show anything on these volumes, but that has been
> reported before. Windows reports them as CIFS or NTFS, depending on
> where you look.
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.
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-07-17 18:39 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 [this message]
2014-07-17 19:43 ` Achim Gratz
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=20140717183915.GT15332@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).