X-Recipient: archive-cygwin AT delorie DOT 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:mime-version:content-type
	:content-transfer-encoding:message-id:date:from:to:subject
	:in-reply-to:references; q=dns; s=default; b=mVppvNwtMtlPbbVBGL9
	gAxp5tVI+8LReC0RPfH5tvpHw4s/iq6a8i88QL0BygYixh+DndnXwFXwVa37xqb/
	4gKjd0KS8g8NjvmwcLquRCldlgYHDxzAT1GGtfg4W9OpZSa7UEZY6uUp2ok2ygiy
	IWqyVRNOsfhX/QBdvJ8E45C0=
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:mime-version:content-type
	:content-transfer-encoding:message-id:date:from:to:subject
	:in-reply-to:references; s=default; bh=YNX86GHs7NepcTp6NTP7BoP3Y
	FY=; b=npJHpGn2NGbMABoPCeLfqdwFDI+1wHrB5af2zCzIJK6BblO3VtftchKwN
	JmGgPtVP/yeqarfEwgPlGVQOjMdIEqeqKe4uHY3Ft3xtyDPcEIZtHA/olFNot3gH
	CkjNQNeu2Elv55+FHgrLBUqw0w4jEK+A0QkdLna77IdVw3zaFg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO: mailbackend.panix.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <22038.38637.802707.846218@compute03.cs.columbia.edu>
Date: Thu, 8 Oct 2015 12:16:45 -0400
From: Jonathan Lennox <lennox AT cs DOT columbia DOT edu>
To: cygwin AT cygwin DOT com
Subject: Re: fstat st_size on open files on Parallels filesystem is wrong
In-Reply-To: <20140423172413.GQ2339@calimero.vinschen.de>
References: <21333 DOT 25325 DOT 11106 DOT 958642 AT compute01 DOT cs DOT columbia DOT edu>	<227151856 DOT 20140421223417 AT yandex DOT ru>	<21333 DOT 26515 DOT 393838 DOT 380071 AT compute01 DOT cs DOT columbia DOT edu>	<20140422081628 DOT GC2339 AT calimero DOT vinschen DOT de>	<21334 DOT 55207 DOT 784319 DOT 488271 AT compute01 DOT cs DOT columbia DOT edu>	<20140423084056 DOT GJ2339 AT calimero DOT vinschen DOT de>	<21335 DOT 61113 DOT 963950 DOT 516021 AT compute01 DOT cs DOT columbia DOT edu>	<20140423172413 DOT GQ2339 AT calimero DOT vinschen DOT de>

Hi, following up on this issue from last year.  The message I'm replying to
is at <https://cygwin.com/ml/cygwin/2014-04/msg00524.html>.

The problem is weird behavior in Parallels Desktop-hosted Windows VMs, when
accessing the host's native Mac OS X filesystem.  See the thread for the
details.

On Wednesday, April 23 2014, "Corinna Vinschen" wrote to "cygwin AT cygwin DOT com" saying:

> > At this point this is looking pretty clearly like a Parallels Tools bug.
> > I'll report it to them.
> 
> Yes, that sounds good.  Given that, I'm wondering if we should try to
> workaround this problem at all or rather wait to see if the vendor will
> fix the issue.

No such luck, despite two major version revisions of Parallels Desktop (I'm
now on version 11.0.2) and moving to Windows 10 as the guest OS -- the bug
perists, unchanged.  So it looks like Cygwin will need to add a workaround
for this filesystem to fix the problem.

The output of /usr/lib/csih/getVolInfo seems to be unchanged from the output
I reported last year.

> Thanks.  This looks pretty much like a filesystem pretending to be
> FAT-like.  There may be another problem lurking, which is, are the inode
> numbers (called "FileId" or "IndexNumber" in Windows) persistant?  With
> FAT this is not the case, and given the above, it might be a problem...
> 
> ...or not.  I just realize that Cygwin doesn't even try to use the
> FileId as inode number on filesystems with FILE_PERSISTENT_ACLS==FALSE
> so, never mind.
> 
> OTOH, does it support hardlinks?  If so, two hardlinks to the
> same file would have different inode numbers on Cygwin.

How would I figure these points out?

-- 
Jonathan Lennox
lennox AT cs DOT columbia DOT edu

--
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