From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Cc: Ruurd Beerstra <ruurdb@wxs.nl>
Subject: Re: Inode number and file size problems in version 3.2.1
Date: Mon, 5 Jul 2021 14:19:56 -0400 [thread overview]
Message-ID: <244fa3f1-08a9-eeb1-6ee0-b0d1c6033ab5@cornell.edu> (raw)
In-Reply-To: <8206027a-a5b5-298f-85bc-01a4a7c02b58@cornell.edu>
On 7/1/2021 12:21 PM, Ken Brown via Cygwin wrote:
> On 7/1/2021 8:15 AM, Ruurd Beerstra via Cygwin wrote:
[...]
>> I found a patch (cygwin1-20210426.dll) with an updated cygwin1.dll. That fixed
>> the hangs.
[...]
>> Note the wrong (changing) times when I use the current 'stat' (the first
>> output is not the same as the 2nd one), while the old version consistently
>> reports correct times, size and inode number. A quick test shows that the 'ls'
>> command (I assume caused by the underlying stat(2) call) reports the same
>> inode number for ALL files.
>> It also reports either a size of "0" or 8192 for ALL files.
>
> Can you tell us something about i:\ivt so that someone could try to reproduce
> the problem? What kind of drive is i:? Does the path "i:\ivt" by any chance
> involve native symlinks or junctions?
Ping?
Can you answer the questions? If there's a bug in the 20210426 snapshot, we'd
like to fix it. But first it would be good if you would test the most recent
snapshot (20210507), available at https://cygwin.com/snapshots/, to see if it's
already been fixed.
Thanks.
Ken
next prev parent reply other threads:[~2021-07-05 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 12:15 Ruurd Beerstra
2021-07-01 16:21 ` Ken Brown
2021-07-05 18:19 ` Ken Brown [this message]
2021-07-06 9:15 ` Ruurd Beerstra
2021-07-06 15:53 ` Ken Brown
2021-07-07 8:50 ` Corinna Vinschen
2021-07-07 17:08 ` Ken Brown
2021-07-01 17:14 ` Brian Inglis
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=244fa3f1-08a9-eeb1-6ee0-b0d1c6033ab5@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=ruurdb@wxs.nl \
/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).