delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/08/22/20:03:17

X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Subject: write() or read() returning ENOENT status
Date: Tue, 22 Aug 2006 19:03:06 -0500
Message-ID: <E05F1FD208D5AA45B78B3983479ECF08C0905F@saturn.p3corpnet.pivot3.com>
From: "Loh, Joe" <joel AT pivot3 DOT com>
To: <cygwin AT cygwin DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k7N03F9C002341

Can anyone tell us what Windows error status gets mapped as ENOENT
return status for wite() or read() system calls?  We have a test program
that runs for hours, sometimes days doing constant I/O to an iSCSI
volume and sporadically we will get an ENOENT return status from either
the write() or read() system calls. 

Thank you in advance.

Joe

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