Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <005601c31e26$77671260$6400a8c0@FoxtrotTech0001>
From: "Bill C. Riemers" <cygwin AT docbill DOT net>
To: "Max Bowsher" <maxb AT ukf DOT net>
Cc: <cygwin AT cygwin DOT com>
References: <16072 DOT 892 DOT 778395 DOT 24290 AT gargle DOT gargle DOT HOWL><003901c31d8c$6ec495f0$78d96f83 AT pomello> <16072 DOT 6666 DOT 10124 DOT 338022 AT gargle DOT gargle DOT HOWL> <00f301c31e12$c29efdb0$6400a8c0 AT FoxtrotTech0001> <00be01c31e15$944d0d50$78d96f83 AT pomello>
Subject: Re: SPARSE files considered harmful - please revert
Date: Mon, 19 May 2003 12:46:19 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165


> Um? By my understanding, making a file sparse can never be dangerous. It
can
> cause sub-optimal performance, but code reading the file doesn't have to
be
> aware of anything special - the OS takes care of it.

I remember there use to be a warning the man page that file system holes can
cause seek offsets to be wrong for programs that do seek's across or into
hole boundries.  The original Linux code only handled when code was loaded
as a result of an mmap which happens for exec's and dlopen.  It could be by
now these restrictions have been eliminated.  I notice the latest GNU cp
info page lists sparse files a filesystem capacity not a kernel capability,
and the logic for --sparse=auto simply copies a file as-is, nothing smart
like checking for the execution bit.

I looked through the NTFS document on MSDN.  It seems at least for NTFS
there is no restriction on what types of files can be sparse.  Of course, if
you make files sparse that are going to be accessed with RW operations, you
are going to fragment the file.

                                            Bill





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