www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/11/17/17:41:51

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <BAY109-DAV9078422072BFE564127AFCF130@phx.gbl>
X-Sender: robbosch AT msn DOT com
From: "Rob Bosch" <robbosch AT msn DOT com>
To: <cygwin AT cygwin DOT com>
Subject: 1.7 preallocate issue?
Date: Mon, 17 Nov 2008 15:40:56 -0700
Message-ID: <005201c94905$8e688b50$ab39a1f0$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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 Nov 14 10:38, Corinna Vinschen wrote:
> It shouldn't be hard to replicate if you modify the rsync statement to
> rsync only one such file.  The strace would be interesting in the first
> place.  You should get an error code from a function called
> fhandler_disk_file::ftruncate.

I can't replicate it the error on demand.  I've used the exact servers and
files that caused the issue in my testing and I cannot get it to repeat on
demand.  The issue, however, still occurs daily.  My analysis of the log
files from rsync do not yield any definitive clues on the issue either (e.g.
specific load, affecting multiple rsync proceses at the same time,
etc...none of these things are happening).  Other posts on "resource
temporarily unavailable" indicates a lack of threads or memory and kernel
modifications address it.  Memory is not the issue here per my monitoring.
Threads do not seem to make sense since the only time the error ever occurs
is when the posix_fallocate function is used in the rsync.

> - Are you perhaps really out of space?
Over 5TB's free on the array

> - Are quotas enabled on the target filesystem and you're hitting your
>   quota?
No OS limitations...the problem only occurred when we moved to more recent
builds of 1.7.  I also think it is related to the build we are using, Cygwin
1.7.0-28, since when I compiled the exact same rsync build/patch/code under
a previous version I did not have the problem (e.g. build date 7/19/08).
 
> - Is the fiber array a local FS or a remote FS?  NTFS/FAT32?  
Direct fiber attached, local FS, NTFS
>   If you don't find any other reason, we would have to check if
>   there are some OS or FS restrictions. 
No OS restrictions...been using the same configuration for two years without
this issue although clearly not on 1.7 with posix_fallocate for that entire
time.

Rob



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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019