X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 9 Oct 2008 12:08:07 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7 preallocate issue?
Message-ID: <20081009100807.GS9289@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <001001c928a8$361f5690$a25e03b0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001001c928a8$361f5690$a25e03b0$@com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Oct  7 12:12, Rob Bosch wrote:
> I've been testing out the 1.7.0-28 build of cygwin using rsync 3.0.3 with
> the preallocate patch.  My destination server setup is a Windows Server 2003
> R2 machine with a fibre array (10TB).  The client is also running the same
> version of cygwin and rsync on a Server 2003 box.  
> 
> I've noticed that when rsync is creating very large files using preallocate
> (20GB+) then I will occasionally get a "Resource temporarily unavailable"
> error returned from rsync on the destination side (the server with the 10TB
> array).  I've removed the file on the destination file system and the file
> will not get recreated using the preallocate option.  When I do not use the
> preallocate option there are no issues with rsync.
> 
> The preallocate patch is pasted below.  The important code segment is here:
> 
> +#ifdef SUPPORT_PREALLOCATION
> +int do_fallocate(int fd, OFF_T offset, OFF_T length)
> +{
> +	RETURN_ERROR_IF(dry_run, 0);
> +	RETURN_ERROR_IF_RO_OR_LO;
> +	/* TODO: Use FALLOC_FL_KEEP_SIZE to avoid the need to truncate. */
> +#if defined HAVE_FALLOCATE
> +	return fallocate(fd, 0, offset, length);
> +#elif defined HAVE_SYS_FALLOCATE
> +	return syscall(SYS_fallocate, fd, 0, (loff_t) offset, (loff_t)
> length);
> +#elif defined HAVE_EFFICIENT_POSIX_FALLOCATE
> +	return posix_fallocate(fd, offset, length);
> +#else
> +#error coding error in SUPPORT_PREALLOCATION
> +#endif
> +}
> +#endif
> 
> Any idea on why this error would occur when using the posix_fallocate
> option?

Not the faintest.  Would you mind to run this under strace and send the
strace output for a run which trips over the "Resource temporarily
unavailable" error to this list?


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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