Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 1 Feb 2005 16:00:58 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Fwd: Re: cp command - problem with sparse Message-ID: <20050201150058.GB31305@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <41FF88C8 DOT 5060604 AT byu DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41FF88C8.5060604@byu.net> User-Agent: Mutt/1.4.2i On Feb 1 06:48, Eric Blake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > This question came up on the coreutils list: > > Does cygwin provide any support for sparse files on NTFS volumes that > support it? lseek() could be patched to use FSCTL_SET_ZERO_DATA when a > seek jumps past the end of a file open for writing, but there is still the > issue of when that file is given the FSCTL_SET_SPARSE attribute. lseek already creates sparse files automatically in a write after lseek, if the lseek seeked more than 128K beyond EOF. 128K is the value which has been found to be the smallest sparse block size at which making the file sparse makes a difference on XP. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/