X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 4C84B3894C0C
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1673714368;
	bh=Vq17v92Qs56t/3EvcaSxZ6Ap0xlxEYsHhIuoiKuN09g=;
	h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=dSLEbGKV9mzqNatS62+piNHPsvmC1jaXJVdhybv7sGp9+RU7Bf7j7qu57r0oP1bs9
	1RJZJ0r9HmUzgOnFc8vBV5lr9nH56a7BWscWLITeXQJbEziYjGA5qTlrX4zmv6SPsJ
	MU3TKgSXzyr8hN2MumK6dufdgywJYiP8/BifchsI=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org C33ED3858421
Subject:	Re: Question about slow access to file information
To:	cygwin <cygwin AT cygwin DOT com>
References:	<797a8935-e38b-0c0f-87d8-b8df1e9fd76f AT cs DOT umass DOT edu>
Message-ID:	<0c9c111e-9e63-bf8c-8049-06fd23f66351@t-online.de>
Date:	Sat, 14 Jan 2023 17:38:42 +0100
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
	SeaMonkey/2.53.14
MIME-Version:	1.0
In-Reply-To:	<797a8935-e38b-0c0f-87d8-b8df1e9fd76f@cs.umass.edu>
X-TOI-MSGID:	9110605a-82b8-4747-82f3-bd21617221f7
X-Spam-Status:	No, score=-3.2 required=5.0 tests=BAYES_00, FREEMAIL_FROM,
	KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW,
	RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE,
	TXREP autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Christian Franke via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Christian Franke <Christian DOT Franke AT t-online DOT de>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 30EGe3Nr016736

Eliot Moss via Cygwin wrote:
> I have a separate drive mounted this way:
>
> d:/ /cygdrive/d ntfs binary,posix=0,user,noacl,auto 0 0
>
> One thing I use it for is to store backup files.  These tend to be 2 Gb
> chunks, and there can be hundreds of them in the backup directory.  
> (The drive
> is 5Tb.)  The Windows Disk Management tool describes it as NTFS, Basic 
> Data
> Partition.
>
> Doing ls (for example) takes a very perceptible numbers of seconds 
> (though
> whatever takes a long time seems to be cached, at least for a while, 
> since a
> second ls soon after is fast).

The problem is the 'noacl' mount option and the fact that POSIX only 
offers the *stat*() functions to retrieve file information. These 
functions always need to provide the full file information, even if only 
a small subset is needed.

To determine the 'x'-permission bits in the 'stat.st_mode' field on a 
'noacl'-mount, Cygwin reads the first bytes of most files (all except 
*.exe, *.lnk, *.com). The 'x' bits are set if the file starts with "#!" 
(script), ":\n" (?) or "MZ" (Windows executable).

On 'noacl' mounts, this behavior could be suppressed by 'exec' or 
'noexec' mount options.

-- 
Regards,
Christian


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -