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 To: cygwin AT cygwin DOT com From: wbp AT nodomain DOT invalid (Will Parsons) Subject: Re: ls slow on top-level directory (was: NFS errors) Date: Mon, 27 Jun 2005 14:50:58 +0000 (UTC) Lines: 22 Message-ID: References: Reply-To: william DOT b DOT parsons AT us DOT westinghouse DOT com User-Agent: slrn/0.9.7.1 (Win32) X-IsSubscribed: yes > However, after some more experimentation, I see the "ls /xp" eventually > does return, after about 17 minutes. So it appears as though NFS kind of > works, but so slowly as to be useless. There is no problem with other > types of network access, e.g., I am logged on to the client machine vai ssh > without problems. It looks like NFS is not completely to blame. It turns out that doing an "ls" on the directory "/c" or "/exports/c" (both mount points for c:) is also unusually slow, though it takes a mere 45 seconds rather than 17 minutes to return. If I export and mount a subdirectory of c:, however, NFS seems to work satisfactorily. I notice that "ls" reports: /bin/ls: hiberfil.sys: No such file or directory /bin/ls: pagefile.sys: No such file or directory "ls hi" completes to "ls hiberfil.sys", and shows the same message. Could this have something to do with the slow response? Although if I do an "ls h*", the above response comes back immediately, not after a wait. - Will -- 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/